> ## Documentation Index
> Fetch the complete documentation index at: https://docs.linquid.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Bulk Link Operations Reference

> CSV import/export, bulk edits, validation rules, and rollback-safe operational workflows

# Bulk Link Operations Reference

Bulk operations are designed for high-volume link lifecycle management.

This area covers all `links import`, `links export`, and `links bulk` workflows from an operator perspective.

## Typical bulk workflows

* initial migration from another platform
* campaign-wide metadata updates
* bulk archive/unarchive actions
* operational export for audit and reconciliation

## Import workflow (safe pattern)

1. Prepare CSV using approved column schema.
2. Validate required fields and domain/path rules.
3. Run a small pilot import first.
4. Inspect created links and assignments.
5. Execute full import when pilot results are correct.

## Common import fields

Typical fields include:

* destination URL
* short code/path
* title
* domain
* campaign assignment
* folder/tag assignment
* optional metadata and notes

## Validation checks before import

* destination URLs are valid and reachable.
* short codes follow allowed format rules.
* target domains are verified/available.
* campaign/folder/tag references are valid.
* duplicates and collisions are resolved.

## Export workflow

Use export when you need:

* backup snapshots before major edits
* reconciliation with external systems
* migration planning between environments
* monthly/quarterly operational audits

## Bulk state-change workflows

Common state changes:

* archive/unarchive batches
* enable/disable groups of links
* recategorize links by folder/tag

Operational guidance:

* always export baseline before destructive changes.
* prefer smaller staged batches for high-risk operations.
* validate analytics impact after state changes.

## Failure handling and rollback

If bulk import results are unexpected:

1. Stop further imports immediately.
2. Isolate affected batch by timestamp/metadata.
3. Use export snapshot to identify delta.
4. Apply targeted rollback (archive/delete/fix records).
5. Re-run corrected batch in small scope.

## Common issues

| Issue                          | Likely cause                        | First action                              |
| ------------------------------ | ----------------------------------- | ----------------------------------------- |
| Import rejects many rows       | Required columns missing/invalid    | Validate schema and rerun pilot           |
| Unexpected campaign assignment | Mapping mismatch in import file     | Re-check campaign identifiers             |
| Duplicate short codes          | Collision with existing links       | Regenerate/adjust conflicted paths        |
| Analytics drift after batch    | Scope/state changed unintentionally | Reconcile with pre-import export baseline |

Related:

* `/user-guides/manual/growth/links-and-settings-reference`
* `/user-guides/manual/growth/tags-folders-utm-reference`
* `/user-guides/manual/data/exports-and-operational-checks`