Prepare CSV link imports with valid destinations, conflict-free aliases, verified domains, and a small-batch review before scaling.
Prepare the data before importing
Use the format supported by the Gods.ly Import screen and keep a clean export of the original records. Review domain, alias, destination, title, and campaign fields before submitting a batch.
Remove duplicate rows, unsupported URLs, and private information that does not belong in public addresses. A clean file is easier to review than a large list of unexplained failures.
Test representative records
Import a small sample that includes the domains and alias types you actually use. Check accepted records and any row-level errors before processing the remaining data.
Reserved routes and existing aliases can prevent an address from being created. Resolve the conflict rather than assuming the import will overwrite a live route.
Keep migration expectations explicit
An import creates supported destination records. It does not automatically preserve another provider’s domains, historical analytics, QR artwork, or unsupported settings.
Verify the new public routes and plan how original shared addresses will continue to work. Keep the old export and service available until continuity has been checked.