Moving from one URL shortener to another does not have to invalidate your campaign links. This reusable migration checklist shows how to inventory existing URLs, prepare a branded domain, preserve destination behavior and UTM structure, compare analytics before and after the move, and test links across websites, social profiles, email, and printed QR codes.
Overview
A URL shortener migration means changing the system that receives a short URL request and redirects the visitor to the final destination. The difficult part is not creating new short links; it is protecting the links already in circulation.
Existing links may appear on your website, social profiles, creator bio pages, email templates, affiliate content, advertisements, downloadable documents, packaging, or printed QR codes. Some may also be saved by customers or embedded in other websites. If the old short-link domain stops resolving before the replacement is ready, those links can fail even when the destination page still exists.
Start by separating two situations:
- Moving links to a new provider while keeping the same branded domain: this may offer the smoothest visitor experience, but it depends on whether you control the domain and whether the new provider supports the required DNS and redirect setup.
- Changing both provider and branded domain: this creates a new public URL. You will need to update published placements where possible and maintain the old domain for as long as necessary.
A migration can preserve the visitor path without preserving historical analytics in the same dashboard. Click records, timestamps, referrers, device information, bot filtering, geographic fields, and attribution rules may be stored differently by each platform. Export what you can before changing anything, then treat the old data as a baseline rather than assuming the new dashboard will reproduce it exactly.
For background on naming and custom domains, see how to create branded short links. If the change is part of a wider domain or campaign cleanup, the link rot audit checklist can help identify other links that need attention.
Checklist by scenario
1. Before changing providers
- Confirm who owns and controls the branded short-link domain.
- Export or record every active short link, destination URL, status, campaign name, creation date, and owner.
- Record query parameters, including UTM parameters, affiliate identifiers, and destination fragments.
- Export available click data and note the date range, timezone, filters, and definitions used by the old platform.
- List where each link is published: website, email, social profile, bio link page, paid campaign, document, packaging, or QR code.
- Identify high-risk links, such as evergreen profile links, customer support URLs, active promotions, and printed materials.
- Freeze unnecessary edits while the inventory is being checked.
A useful inventory can use these columns:
| Short URL | Final destination | Placement | Campaign or UTM | Priority | Owner | Test result |
|---|---|---|---|---|---|---|
| go.example/offer | Landing page URL | Email and bio page | spring_offer | High | Marketing | Pending |
2. Prepare the new provider
- Confirm that the new service supports your required branded domain, path format, redirect behavior, destination editing, and analytics fields.
- Review any import or bulk-creation option, and confirm which fields it accepts.
- Decide whether old slugs will remain identical. Keeping them can reduce update work; changing them may be necessary if naming rules or conflicts differ.
- Prepare the DNS record requested by the new provider. This may involve a CNAME, A record, or another configuration, depending on the service and domain setup.
- Check certificate, HTTPS, and domain-verification requirements before launch.
- Set up workspace access, permissions, backups, and an owner for ongoing maintenance.
DNS changes may take time to appear consistently. Do not remove the old configuration simply because the new dashboard shows a successful verification. Verify the domain from multiple networks or testing locations where practical.
3. Keep the same branded domain
If the old provider and new provider can use the same custom domain, plan a controlled cutover. First recreate or import the short links in the new system. Then test them on a temporary hostname or through the provider’s preview method if available. At the agreed change window, update DNS or the relevant routing configuration.
During the cutover, monitor priority links directly. A successful redirect should reach the intended destination, retain the required parameters, use HTTPS where configured, and avoid unexpected intermediate pages. Do not assume that an identical slug automatically means identical behavior; confirm each important route.
4. Change to a new branded domain
When the public domain changes, keep the old domain active if the former provider or your domain configuration allows it. Create replacement links under the new domain, then update editable placements such as websites, email templates, social profiles, link-in-bio pages, affiliate pages, and campaign dashboards.
Printed QR codes require special care. A QR code that contains the old short URL cannot be updated by editing the destination in the new platform unless the old URL still resolves through a system you control. Treat every printed code as a permanent dependency and test it from a phone camera before and after the migration. The guide to dynamic QR codes for marketing covers the maintenance implications in more detail.
5. Scenario test matrix
| Location | What to test | Pass condition |
|---|---|---|
| Website | Click and inspect the final URL | Correct page loads without a broken or unexpected redirect |
| Social profile | Open from a logged-out mobile browser | Page loads clearly and remains mobile-usable |
| Test the actual sent message or template | Link opens and campaign parameters remain intact | |
| Bio link page | Tap from a phone and review analytics | Correct destination loads and the click is recorded as expected |
| Printed QR code | Scan under normal lighting and distance | Code resolves to the intended destination |
| Affiliate link | Follow the complete redirect chain | Required tracking identifier is retained |
What to double-check
Redirect and destination behavior
Check whether the new system uses the redirect type and chain expected for your use case. A short link should not add a different destination, remove a required query parameter, or create a loop. Compare the final URL character by character where tracking matters. Pay particular attention to capitalization, trailing slashes, encoded characters, fragments, and affiliate parameters.
Short links are not a substitute for a sound destination structure. If your project also involves sending visitors into a mobile app, compare the behavior of short links with deep links in this guide to deep links and regular URLs.
Analytics continuity
Use this comparison before switching:
| Analytics area | What may continue | What may need a new baseline |
|---|---|---|
| Historical clicks | Exported reports and saved summaries | Historical records inside the new dashboard |
| UTM attribution | Parameters preserved in destinations | Channel grouping and reporting rules |
| Referrers | Some source data may appear | Field names, sampling, or missing referrer values |
| Devices and locations | Comparable categories in some systems | Definitions, privacy treatment, and available detail |
| Conversion reporting | Downstream analytics if tagging remains consistent | Platform-specific click-to-conversion connections |
Preserving analytics starts with consistent naming. Use the same campaign, source, medium, and content conventions where possible, but document any changes. For a practical tagging workflow, review how to track clicks with UTM parameters and short-link analytics.
Domain, security, and trust
Confirm that the branded domain is spelled correctly, resolves over HTTPS, and is not being used for unrelated or unclear destinations. Review who can create links, edit destinations, and access click data. Retire unused slugs carefully rather than reassigning them immediately, since an old URL may still be referenced somewhere. The short-link security guide provides a useful review framework.
Common mistakes
- Deleting the old account too soon. Keep exports, configuration notes, and access until all important links have been tested and the retention plan is clear.
- Assuming a provider import is complete. Compare the source inventory with the imported links. Missing destinations, duplicate slugs, and altered parameters can be easy to overlook.
- Changing slugs without updating placements. A new short URL does not automatically replace one in an old post, email, PDF, or printed asset.
- Measuring only total clicks. Compare dates, campaign labels, destinations, and traffic context. A total-click difference may reflect filters or definitions rather than a real performance change.
- Ignoring bio and affiliate links. Creators often reuse a small number of profile links across multiple platforms. Check the bio link page and every prominent button, not just the page’s main URL. For affiliate workflows, see the affiliate link management guide.
- Skipping mobile tests. A link that works in a desktop browser may still lead to a poor mobile page, an app-store mismatch, or an unexpected browser handoff.
- Reusing retired slugs immediately. Keep a record of old destinations and avoid assigning a previously used path to a different campaign without a clear review process.
When to revisit
Revisit this migration checklist before a seasonal planning cycle, rebrand, domain change, provider change, or major campaign launch. It is also useful during a quarterly link audit, especially when a team member leaves, a creator changes their bio page, or a printed QR campaign is refreshed.
At minimum, schedule a recurring review of your short-link inventory. Confirm that high-priority links still resolve, destinations are current, UTM conventions remain consistent, and analytics are being recorded in the expected dashboard. Update this workflow when your provider changes its export options, DNS requirements, redirect behavior, analytics fields, or account permissions. Browser behavior and social-platform handling can also change, so repeat tests on the devices and channels that matter to your audience.
Final action list: export the old data, complete the inventory, prepare DNS, recreate or import links, preserve old-domain access where possible, update editable placements, test every scenario in the matrix, compare analytics baselines, and document the final configuration. A careful migration is less about switching a dashboard and more about maintaining every public path that leads people to your content.
