Skip to main content
Start the Short.io import from Biqli’s migration area and follow the connection or import prompts. Select the destination workspace and review domain mapping before confirming. Afterward, check a sample of short URLs, destinations, aliases, and active states. Test each branded domain and leave the old service available until validation is complete. The importer only carries the fields identified in its review step. Recreate unsupported provider-specific behavior in Biqli where needed.

​
Prepare

Confirm Short.io account access, source domains, destination workspace, and available quota. Keep a source export or inventory so you can compare results.

​
Import and verify

  1. Open the Short.io migration in Biqli.
  2. Complete the connection or file instructions.
  3. Review domain mapping and fields included by the importer.
  4. Start the migration and investigate failed rows.
  5. Compare a representative sample of short URLs and destinations.
  6. Test every custom hostname before moving DNS or closing the source service.
Historical reports and provider-only features can remain outside the imported record. Document and rebuild required behavior before the final cutover.

​
Common migration questions

​
Will the import move DNS automatically?

No. Domain DNS remains an external change. Connect and verify the hostname in Biqli, test it, and plan the cutover separately. No. Keep Short.io available until aliases, destinations, custom domains, and required behavior have been verified in Biqli.

​
What should I do with failed rows?

Review each error for an invalid URL, conflicting alias, missing domain, quota, or unsupported source setting. Correct and retry only the affected records.