Skip to main content
Start the Bitly import from Biqli’s migration area and follow the authorization or import prompts shown there. Select the destination workspace and review any domain choices before starting. After import, compare a sample of destinations, aliases, and active status with Bitly. Test branded domains separately and update DNS only when Biqli instructs you to do so. Keep the Bitly account active until the imported links have been checked.

​
Prepare

Export or authorize the Bitly data using the exact method shown by the Biqli importer. Confirm the destination workspace, available link quota, and ownership of every branded domain involved.

​
Import and verify

  1. Start the Bitly migration from Biqli.
  2. Complete the requested connection or file step.
  3. Review the import summary and domain choices.
  4. Start the import and inspect any row-level failures.
  5. Compare a representative set of aliases, destinations, and statuses.
  6. Test each branded hostname before moving DNS or ending Bitly service.
Provider-specific settings and historical analytics are not guaranteed unless the importer explicitly lists them. Recreate unsupported behavior in Biqli and keep the original export as a migration record.

​
Common migration questions

​
Does importing change Bitly?

The Biqli import creates destination records. Do not assume it removes or edits the source account. Check for alias conflicts, invalid destinations, missing domain mapping, quota, or unsupported provider data. Retry the corrected record instead of repeating the full import blindly.

​
When can I end Bitly service?

Only after representative links, every branded domain, and required campaign behavior work from their final public URLs.