Migrate links
Plan a link migration as a routing change. Export source data, preserve a backup, preview field mappings, and test representative destinations before switching public traffic.
Preview Branch JSON
MCP preview_branch_links validates supplied Branch link JSON without fetching URLs or writing to your workspace. Ask the MCP client for the current inputSchema, then supply 1–100 exported link objects in its links array and a required HTTP(S) fallbackUrl. Optional defaults are iosUrl, androidUrl, and domainId.
Review every warning, notice, and blocked row in the result. Unsupported controls can block a row rather than silently changing its meaning. A preview is a proposed mapping, not a completed migration or a guarantee of feature parity.
Create reviewed links
Use server links or an MCP token with production link management to create approved mappings. Choose a stable key per source record and save a mapping from old URL to new LinkRunway id and shortUrl.
Inspect duplicate when resuming a partially completed migration. A conflicting 409 requires review of the existing mapping; do not automatically invent a new key and distribute two links for the same record.
Test before switching
Check desktop fallback, installed iOS and Android apps, app-not-installed behavior, campaign metadata, partner ownership, expiry, and privacy-suppressed visits. Verify custom-domain association files on physical devices.
LinkRunway cannot take control of a third-party provider's domain. Replacing a link in future campaigns does not redirect URLs already printed or distributed. Keep the previous provider available while you manage redirects or replace existing placements.
Rollback and cleanup
Retain the old-to-new mapping and your previous DNS/routing configuration. Change a small batch first, monitor actual outcomes, and keep a rollback path. Do not archive old production links until you understand their remaining traffic and retention needs.
For unsupported mappings, send a sanitized example to support@linkrunway.com, excluding credentials and customer data.