BoltForge Convert Mode Migration (Delivery)

BoltForge Convert Mode Migration (Delivery)

1. 01

   Confirm the client's current host and platform before opening Convert mode

   Convert mode rebuilds WordPress, Duda, and Squarespace sites into owned Next.js code. Pull the live URL, hosting provider, and DNS registrar from the client kickoff form so the rebuild targets the right source and the cutover plan is realistic.

2. 02

   Run Convert mode against the client URL and capture the fidelity report

   The fidelity report shows what transfers versus what needs manual rebuilding. Flag any page, form, or integration the report marks as partial before quoting the migration as a fixed-scope deliverable.

3. 03

   Rebuild flagged pages through the prompt-to-code agent loop

   Describe the missing section in plain English and refine through chat until the output matches the client's approved design. Budget 2 to 4 refinement passes per flagged page; the agent loop rarely lands a complex layout on the first prompt.

4. 04

   Reconnect native authentication, payments, and booking

   BoltForge ships Clerk authentication, Stripe payments, and booking systems as native modules. Rebind the client's Stripe keys and Clerk instance in the workspace settings, then test one live booking and one test payment before handoff.

5. 05

   Set the client's domain, SSL, and backup schedule on their hosting

   Point the custom domain at the new Next.js build, confirm SSL issuance, and enable daily backups. If the client brings their own AWS, Convex, or DNS, document the account owner in the delivery handoff so the agency is not the single point of failure.

6. 06

   Verify the client can edit text and photos on the live page

   The Care plan includes free live-page editing for text and photos. Walk the client through one edit during handoff and leave a short editing guide in the shared drive so routine copy changes do not become billable tickets.

7. 07

   Archive the old site and close the migration ticket

   Keep the previous host live for 14 days after cutover, then decommission. Record the source URL, fidelity report, and final build commit in the client workspace so a future agency operator can trace what changed.