Download your workspace records
In Settings → General → Export, choose Download .zip. The download containslinks.csv, your-pages.csv and workspace.json. The JSON includes saved contacts and link associations, with a per-table list of the exported fields and exclusions.
The export contains allowed metadata across your workspace. It leaves out credentials, private stored objects and unreviewed or shared payloads. Pages are read live, so the export is not a frozen backup. Keep it private: saved contact details can include email addresses. Security and data covers how long records are kept and how to delete them.
Export hosted records
Call 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_evidence withsubject: "link" or subject: "target" and the observation identifier for retained 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 to preview field mapping and reconcile destination readback.
Sync an optional local ledger
Follow CLI connection first. Sync connects one ledger to one hosted project. Use the CLI installed through that guide for the commands below. Preview uploads before running a full sync. Uploads can create recurring watches; review their schedule and check allowance first. Pull-only sync reads cloud history.Preview sync, upload expectations and recover a pull
Preview sync, upload expectations and recover a pull
Review what will cross the connection
--include-wanted when you intend to include them.--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.Recover an expired feed
For HTTP 410 withCURSOR_EXPIRED, preserve the returned recovery details and the missing interval. Published CLI 0.6.13 recovers source events from a watch export and target events from the target list. It saves the complete paged snapshot before resuming that feed. Source recovery can need exports:create; target reads need watches:read, alongside events:read for the feeds. Choose task scopes before recovery.A snapshot recovers current state. It cannot reconstruct expired transitions. Keep the history gap visible and leave the other feed’s cursor intact. A custom or older client without the required snapshot adapter must stop and retain its cursor; current code reports RESYNC_SNAPSHOT_UNAVAILABLE. Follow the response and your installed version. Keep the old cursor until recovery succeeds.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.