URL Shortener Migration Checklist: Domains, Links and Data
Changing a shortener's DNS record does not move its links. It changes which service receives requests for the domain. The new service still needs a matching destination for every short URL you intend to preserve.
A URL shortener migration checklist should therefore cover domain control, exact link mappings, QR destinations, historical data, cutover tests and rollback. Start with ownership. It determines which URLs you can move and which must remain with the original provider.
If you are switching from Rebrandly, Bitly or Dub, use this checklist before cancelling an account or changing a live domain. The work can be modest when you only want a new home for future links. Moving years of published links is a different job.
Ownership Inventoryโ
Group your links by hostname, the domain portion of each URL. For every hostname, record the registrar, DNS administrator, renewal owner and current shortening service.
There are two distinct situations:
- You control the domain or subdomain, such as
go.example.com. You may be able to keep the full short URLs by reproducing their paths on a compatible service and then changing DNS. - The provider controls the domain, such as
bit.lyorrebrand.ly. You cannot point that hostname at another shortener. Existing URLs remain dependent on the provider's service and account terms.
A domain bought through a shortening platform needs closer inspection. Find out who manages its registration and whether transferring it requires the platform's assistance. Rebrandly distinguishes domains you connect from your own registrar from domains purchased through its service, where control is more limited.
For agency accounts, confirm that the client owns the domain and has authorised the move. Access to a shared dashboard is not proof of ownership.
If you are still comparing Rebrandly alternatives for agency link management, settle those ownership questions before comparing plan limits. Your migration options depend on them.
Link and QR Destination Inventoryโ
Create one row per published short URL. Keep the full URL, its exact path, destination URL, owner, campaign and any expiry or routing rules. Preserve query strings rather than exporting only the landing page's base address.
Record where each link appears. A path used in an editable LinkedIn post is easier to replace than one printed on packaging or included in a delivered email.
Prioritise checkout, donation, booking and login links, along with anything printed or used in an active campaign. Recent click counts help prioritisation, but a quiet link may still be needed for a future event or seasonal campaign.
Inspect printed QR codes by decoding what they contain:
- A QR code containing the final website URL is independent of the shortener, unless that website route itself relies on it.
- A QR code containing your branded short URL relies on that domain and path continuing to redirect correctly.
- A QR code containing a provider-owned URL remains dependent on that provider. Creating a new QR image elsewhere does not change the code already printed.
For dynamic QR code campaigns, distinguish the image from the redirect behind it. Keeping the image useful requires preserving the encoded URL's behaviour.
Transferable and Nontransferable Dataโ
Treat redirect mappings, reporting history and platform settings as separate migration tasks. A successful link import does not establish that all three moved.
| Item | What to establish before moving |
|---|---|
| A custom domain you control | The target service accepts it and can serve HTTPS correctly |
| Existing short paths | Exact paths can be recreated, including case, unusual characters and any nested paths |
| Destination URLs and UTMs | The full destination survives export and creation without losing or duplicating parameters |
| Historical analytics | An export is available, and you know whether the target can import it or you must archive it separately |
| Tags, folders and permissions | Each field has a target equivalent or an agreed replacement |
| Routing, expiry and integrations | Required behaviour can be reproduced and tested |
Rebrandly provides analytics exports on paid plans, subject to account limits. Keep those reporting exports separate from the link inventory you need to recreate redirects.
Archive the date range, time zone, metric definitions and export date with each report. Combining old and new click totals without checking their definitions can produce a misleading trend.
Do not carry over provider-specific link IDs as if the new service issued them. Maintain a mapping between old identifiers, full short URLs and new identifiers for integrations and reporting.
For a Bitly starting point, the Bitly to SimpleURL setup guide covers the switching workflow. Apply the ownership and continuity tests here before making a live DNS change. Old provider-owned URLs are not transferred by that change.
Cutover Testsโ
First ask the target provider how it stages an existing domain and its links while traffic still reaches the old service. Confirm the method for testing redirects and issuing the HTTPS certificate. If staging requires a traffic change, agree to a maintenance window rather than assuming uninterrupted service.
Recreate the mappings, then test every required path automatically where practical. Inspect business-critical and printed links manually too.
Your tests should establish that:
- The full short URL reaches the intended destination without a certificate error, loop or unexpected intermediate page.
- Destination parameters survive, including UTMs and any application-specific values.
- A query parameter added to the short URL behaves as intended. Do not assume every service forwards or merges it the same way.
- Case-sensitive paths, trailing slashes and unusual paths behave according to the inventory.
- Routing, expiry and fallback rules match the agreed specification.
- Printed QR codes work on the devices your audience uses.
Test link-creation integrations as well. Check authentication, response fields, duplicate handling and error responses. Switching an automation's app connection is insufficient if the next step expects an old provider's link ID or JSON field.
Freeze edits during the final export and import, or capture and reconcile changes made between them. Otherwise, a link created ten minutes before cutover may be missing from the new system.
DNS results can differ during the transition because resolvers cache records. If you lower the record's time to live (TTL), do it early enough for the previous cache period to expire. Keep both services able to serve the required paths during the agreed overlap where the providers support that arrangement.
Rollback and Costsโ
Record the old DNS values before editing them. Name the person who can restore them, the failure conditions that trigger rollback and the period during which the old account must remain operational.
Restoring DNS does not instantly move every visitor back. Cached records can keep sending some requests to the newer service. Preserve the mappings on both sides until you have checked the result.
If new links were created after cutover, account for them before rolling back. The old service may have no destination for those paths. A short pause in link creation makes that reconciliation easier.
Budget for inventory cleanup, export access, link recreation, testing and integration changes. Add subscription overlap and domain renewal or transfer charges where applicable. Include reprinting only where an encoded URL cannot be kept working.
Compare the current SimpleURL subscription limits and billing options against your full inventory. A plan suitable for this month's new links may still be unsuitable for recreating a large archive. Confirm how migrated links count towards its limits.
Worked Example: Moving 300 Published Short Linksโ
Consider this illustrative inventory, not a customer case study:
- 240 URLs use a company-controlled subdomain,
go.example.com. - 60 URLs use
rebrand.lyand remain with Rebrandly unless their published placements can be replaced. - 18 printed QR codes point to URLs among the 240 branded links. They are not 18 additional mappings.
The team wants to preserve the 240 branded URLs and create future links on SimpleURL. It archives historical reports separately rather than assuming an analytics import.
SimpleURL's batch link creation API documents up to 100 short URLs per request, with fields for a custom keyword and configured domain. For 240 compatible mappings, that means at least three requests: 100, 100 and 40. Failed records or retries may require more. Confirm account access, quota and path compatibility before using this route.
During testing, three paths fail compatibility checks. The migration pauses until the team can reproduce those paths or agree how to keep their existing URLs working. A 237 out of 240 success rate still leaves three published links unresolved.
Here is a sample transition-month budget. Labour and the old subscription price are assumptions. The new subscription uses SimpleURL's published Pro monthly price when this example was prepared; it does not include a managed migration service.
| Cost Item | Example Amount in USD |
|---|---|
| Inventory, recreation and testing at 8 hours ร $75 | $600.00 |
| One additional month of the old service, assumed | $29.00 |
| One month of SimpleURL Pro at the listed monthly rate | $24.99 |
| Transition-month total | $653.99 |
Taxes, domain charges, additional capacity, reprinting and separately quoted support are excluded. The $24.99 is a subscription cost, not a one-time migration fee. Annual billing has a different payment commitment, so compare the amount charged as well as the advertised monthly equivalent.
Reusable Migration Checklistโ
- Confirm registrar access, DNS control and ownership for each domain.
- Export every required short URL with its full destination and rules.
- Decode printed QR codes and match them to the inventory.
- Separate provider-owned URLs from domains you can move.
- Archive historical analytics and record their definitions and time zone.
- Confirm target capacity, path compatibility and a staging method.
- Recreate mappings and resolve failed records before changing DNS.
- Test redirects, HTTPS, parameters, QR scans and integrations.
- Freeze changes or reconcile the final differences.
- Save rollback records, retain the agreed overlap and monitor failures.
- Confirm retention and continuity requirements before cancelling anything.
Confirm the Migration Scope with SimpleURLโ
SimpleURL documents branded domain short links, custom keywords and an API route for batch link creation. Those features provide a starting point for assessing your inventory.
A CSV importer, historical analytics import, managed migration, contractual uptime commitment or enterprise identity controls need explicit confirmation. A batch creation endpoint does not establish those capabilities.
Ask SimpleURL support at contact@simpleurl.tech to review your domain list, link count, unusual paths and required features before committing. Request the supported method, applicable limits and any assistance charges in writing. If you are also evaluating Dub alternatives, use the same inventory and acceptance tests for each candidate.
Migration Frequently Asked Questionsโ
Can I keep all existing short URLs?โ
Only where you control the hostname and the target can reproduce the required paths and behaviour. Provider-owned URLs cannot be moved by editing your own DNS. Review their ongoing service and account requirements separately.
Will historical clicks appear in the new dashboard?โ
Do not assume so. Confirm export and import support independently. If history cannot be imported, retain a dated archive and mark the change of reporting system in your analysis.
Can I promise a migration with no downtime?โ
Promise only the continuity your staging, certificate, mapping and cutover tests establish. Domain access, cached DNS responses and platform restrictions can affect the transition.
