Controlled import
CSV rows are processed with visible progress, item errors, and cancellation instead of loading the entire file at once.
Migration to Gods.ly
Move from Bitly without losing route ownership or history.
A safe migration starts with evidence. Inventory active and historical links, custom domains, tags, destinations, titles, expiration, and access rules before creating target records.
Open Import & ExportClear row mapping
Every accepted source row receives one stable result and a verification status.
Cutover discipline
DNS and traffic move only after route sampling, count checks, and rollback rehearsal.
Export and classify the source
Separate active, archived, expired, protected, and deleted links. Record domain, alias, destination, title, creation time, and any campaign or tag context available from the source.
Do not assume an exported row fully represents custom-domain or password behavior.
Import through a private job
Gods.ly stores the upload privately, verifies the file, processes rows within safe limits, and creates links using the same checks as the dashboard. Valid rows can succeed while invalid rows receive a downloadable error report.
A retry uses the source row’s unique fingerprint so it does not duplicate links that were already accepted.
Verify before changing traffic
Compare source and target counts by disposition, test representative high-traffic routes, check custom domains, and measure redirect status and destination parity. Keep a rollback map until the agreed stabilization window closes.
Any conflicting reserved alias needs an explicit replacement and communication decision.
Common questions
What teams ask before they start.
Can an import partially succeed?
Yes. The job reports accepted and rejected rows separately and provides an error file without presenting the whole batch as successful.
Should DNS be changed before import?
No. Import, validate, and rehearse rollback before moving a custom domain to the new routing edge.
Start with a real workflow