Inventory first
List still-published links, printed QR codes, branded domains, active campaigns and links that still generate traffic. The rest can be archived or imported later.
Migration guide
Migrate from Bitly, Short.io or Rebrandly without breaking links
A link migration is not just copy and paste. You need to know which links still live, which slugs matter, which domains are used and which assets cannot be edited.
Useful for
- Accounts with link history
- Agencies taking over a client
- Teams wanting to clean their inventory
Business impact
- Sample-based migration.
- Important slugs preserved.
- Progressive domain cutover.
Guardrails
- Do not cut the old tool too early.
- Test critical links before switching.
Preserve what is visible
Slugs, domains and QR codes already visible to customers should be treated as priorities. A mistake on these links is immediately visible, unlike a forgotten internal link.
Import by batches
Start with a representative batch: a few simple links, one campaign, one domain and one QR. Check redirects, analytics and ability to fix things before importing the rest.
Controlled cutover
Keep the old tool available during transition. Full cutover should come after tests, not before, especially if printed assets or partner links still exist.
Related guides
Continue with the closest workflows.
For the next step, see custom domain for short links.
For the next step, see choose a campaign URL shortener.
For the next step, see print QR code checklist.
For the next step, see Bitly, Short.io and Rebrandly migration.
Should all old links be migrated at once?
No. Start with still-active links, printed QR codes, partner links and visible domains. Archives without traffic can wait or remain documented without being moved immediately.
How do you avoid breaking QR codes or already shared assets?
First identify already published slugs and domains, then test by batches. Each batch should check redirect, analytics, domain, QR and fallback before cutting over from the old tool.