What can and cannot come with you
The domain question
This is what determines your sequencing. If your links are on the old provider’s domain, they cannot follow you. Keep that account alive as long as those links matter, and use new links from now on. If they are on your own custom domain, they can — but DNS points at one provider at a time, so every existing back-half must exist here before you switch, or they break at the moment of cutover.1
Export everything from the old provider
Back-half and destination at minimum. Tags and groups if you can get them.
2
Add the domain here, but do not point DNS at us yet
Complete verification. Serving continues from the old provider throughout.
3
Recreate every link with its exact back-half
Same back-half, same destination. This is the step that must be complete.
4
Reconcile
Compare the full list here against your export. Every back-half must be present and pointing at the right place.
5
Switch DNS
Traffic moves to us as DNS propagates. Because the back-halves match, in-flight links keep resolving.
6
Watch for 404s
A back-half that was missed shows up as a not-found. Create it immediately — the link is already out in the world.
Importing
create_shortlink is multipart, which is why fields are passed as files rather than data. See Creating links.Reconciling before cutover
Handling failures
DUPLICATE_ENTRY
DUPLICATE_ENTRY
That back-half already exists on this domain. Usually a re-run of a partially completed import; verify the existing link points where it should before treating it as done.
INVALID_PARAMETER on back_half
INVALID_PARAMETER on back_half
The other provider allowed a character we do not, or the length differs. These need a decision per link, and the old link will break at cutover — a redirect from the old system, if it offers one, is the only way to preserve it.
FEATURE_LIMIT_EXCEEDED
FEATURE_LIMIT_EXCEEDED
Your plan’s link allowance is exhausted. Check
get_feature_limits against your export size before starting, not halfway through.