Skip to main content
Start the Rebrandly import from Biqli’s migration area and complete the connection or import prompts. Choose the destination workspace and carefully map any branded domains presented by the importer. When it finishes, verify representative destinations, aliases, and link status. Test links on every migrated hostname before changing or removing the previous setup. Imported analytics can differ from historical Rebrandly reports. Treat the migration screen as the source of truth for the data types included.

​
Prepare

Confirm access to the Rebrandly account, select the intended Biqli workspace, and review quota and custom-domain ownership. Export a backup from the source where available.

​
Import and verify

  1. Start the Rebrandly migration in Biqli.
  2. Complete the authorization or import prompt.
  3. Review hostname mapping and the import summary.
  4. Run the import and inspect failures individually.
  5. Compare sample aliases, destinations, and active states.
  6. Test every branded hostname before changing DNS.
Do not terminate the old service on the same day as the first import. Allow time for link testing, duplicate resolution, and recreation of any provider-specific settings that Biqli does not import.

​
Common migration questions

​
Are historical analytics included?

Only data explicitly identified by the importer should be expected. Preserve source reports separately when history matters.

​
What causes an alias conflict?

The same alias already exists on the mapped Biqli domain. Decide which public URL should remain before changing either record.

​
When should DNS move?

After the domain is connected, the imported sample is verified, and your team has a rollback plan.