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

# Sync history and export your records

> Preview expectation uploads, pull independently cursored feeds, recover expired history, and export monitored records without changing local campaign notes.

Export hosted placement records through your connected agent or API. If you also keep a local ledger, sync can copy observations and event history into it. Your local declarations and campaign notes stay under your control.

## Export hosted records

Call [export\_link\_watches](/reference/commands/export_link_watches) with the project and filters you need. Keep those filters unchanged while paging. Save every returned page and follow its continuation cursor until the export finishes. One page is not a complete export.

The export covers monitored records in the selected scope. It does not establish a complete backlink inventory for a domain. Use [get\_link\_evidence](/reference/commands/get_link_evidence) or [get\_target\_evidence](/reference/commands/get_target_evidence) for retained observation snapshots. Expired raw evidence leaves metadata available; a fresh check cannot reproduce an old page.

For records held in another tool, follow the [CRM and sender handoff guide](/guides/crm-sender-handoff) to preview field mapping and reconcile destination readback.

## Sync an optional local ledger

Follow [CLI connection](/guides/connect-cli) first. Sync connects one ledger to one hosted project. You need the supplied toolkit or an authorized checkout for the local commands below.

## Review what will cross the connection

```bash theme={null}
agentlinkops sync --dry-run
agentlinkops sync --pull-only
```

The dry run reports the planned upload without network work. Pull-only retrieves cloud history. Review the default selection before pushing expectations. Wanted placements require `--include-wanted` when you intend to include them.

```bash theme={null}
agentlinkops sync
agentlinkops status
agentlinkops diff
```

Use `--push-only` when you intend to upload expectations without pulling feeds. Keep your saved connection tied to the same workspace and project. For a different identity, prepare a separate ledger so existing mappings cannot attach to another account.

## Recover an interrupted pull

Source and destination feeds use separate cursors. Sync applies each page before advancing its cursor, and replay deduplicates events. An expired cursor triggers snapshot recovery. Inspect the reported recovery outcome; a gap means some event history is no longer retained.

After a network failure, rerun the same intended sync. For authentication or identity refusal, correct the connection first. Keep local notes and tags intact while resolving cloud access. Do not delete cursors merely to silence an error.

## Export a reviewable report

```bash theme={null}
agentlinkops report --out link-report.html
```

Read [the ledger guide](/ledger) before sharing report files, especially if you include notes. This HTML report reads your local ledger; use the hosted export above when you need records from AgentLinkOps.

See [evidence](/evidence), [webhooks](/guides/webhooks) and [troubleshooting](/guides/troubleshooting) for retained observations, notifications and recovery.