How to migrate from Bitly to Dub
Technical infrastructure migrations vary a lot depending on the tool — these are the general steps that apply to most cases.
- 1
Export your configuration and data from Bitly
Check Bitly's documentation for exporting projects, configuration and integrations — the exact format depends on the service, but almost all offer some export path for paid accounts.
- 2
Prepare the Dub environment
Deploy Dub in a staging environment first (not production) and replicate the base configuration before moving any real data.
- 3
Migrate in pieces and validate each one
Move one project or integration at a time instead of all at once, checking that each piece works in Dub before moving on to the next.
- 4
Update integrations that depended on Bitly
Any external service (CI/CD, webhooks, SDKs) that pointed at Bitly needs to be reconfigured to point at your new Dub instance.
Before cancelling Bitly
Before cancelling Bitly, confirm no production service still depends on it by checking recent access logs.
Ready to deploy Dub?
Full profile with license, tech stack and ready-to-copy docker-compose.
View Dub's profileThese steps are a general guideline — the exact export menu can vary depending on Bitly's plan and version.