Destination inventory
Every source link receives a copied, replaced, or retired disposition.
Bio Page migration
Move a link-in-bio page with every destination accounted for.
Treat every visible block as a content decision. Record its label, destination, order, media dependency, visibility, and purpose before rebuilding the page in Gods.ly.
Build the replacement pageSafe visual rebuild
Structured themes replace unsupported script or unsafe custom markup.
Previewed cutover
Mobile, keyboard, sharing metadata, and public status are checked before the profile URL changes.
Capture more than the visible URL
Record link labels, order, scheduling, embeds, social profiles, page title, description, theme, and any custom domain. Check whether media files can be exported and whether their licenses permit reuse.
Unknown or missing files stay private for review instead of being copied directly onto the public page.
Rebuild with supported blocks and routes
Create managed short routes for destinations that need independent analytics or future updates. Add them to a Bio Page in the intended order and preview the actual public renderer.
Use descriptive labels and accessible contrast instead of relying on image-only actions.
Change the profile link after acceptance
Test the target on mobile, desktop, keyboard navigation, sharing previews, and a clean browser without a dashboard session. Keep the source page during a short overlap when possible.
Choose search visibility in the page’s SEO settings. Direct sharing works independently of search indexing.
Common questions
What teams ask before they start.
Will custom scripts be copied?
No. Unsupported executable markup is not migrated; its business purpose needs a safe supported replacement.
Can old links become managed short routes?
Yes. Create a route for each destination that needs independent lifecycle or analytics, then place it on the Bio Page.
Start with a real workflow