Migrations
Three migrations are documented today; the workflow is the same for each one.
- Export - pull a CSV from your current shortener.
- Bulk-import - POST the rows in batches to
/v1/workspaces/{ws}/links/bulk. - Cut over the custom domain - register the hostname in Elido
(TXT verify + CNAME), keep the old CNAME live, flip when Elido’s
status reaches
active. - Repoint integrations - update API callers, webhooks, and any pixels.
Pick your provider
- From Bitly - including the Bitly v4 API → Elido endpoint mapping.
- From Rebrandly - including workspace, role, and slashtag mapping.
- From Short.io - including domain-level pixels → workspace pixels.
Things that don’t migrate cleanly
- Historical click data. Vendors only export aggregated daily counts. Elido’s analytics start the moment you cut over - keep the source CSV around for retrospective reports.
- Vendor-specific rules. Password gates and access codes don’t have a 1:1 equivalent yet. Use smart links for geo / device / time targeting; pair with a custom interstitial for password-style gates.
- Webhook secrets. Rotate to a new secret on the Elido side and re-sign on receivers; old HMACs won’t verify.