Skip to content
WebrenewDocs

Files and integrations

Download your Launch site's code

Take a saved site into a standalone Next.js project and understand which hosted services need replacements.

Who this helps
Owners or developers who want an independent code copy or a self-hosted deployment.
Before starting
Save the site. Arrange a development environment and a host that supports the exported Next.js project.
Done when
The downloaded project builds, and every required hosted dependency has an explicit migration plan.

01

Download the saved version

Open the website editor, select Code, then Download code in the files panel.

The download uses the saved version. Resolve save or source-boundary errors before trying the export again.

  1. Wait for the saved indicator.
  2. Select Code → Download code.
  3. Extract the archive and read its README.md.
  4. Keep an unchanged copy before adapting the project.

This is the Launch export. Older purchased-code downloads have a different structure and use the separate Hosting setup guide.

02

Understand the project

The archive includes the site's source, theme, adapted Next.js pages, and a snapshot of its business details and posts.

The app and components folders hold page code. theme.css holds the theme. The wr folder supplies the exported runtime and data.

Image references still point to their existing hosting locations. This is not an archive of every original media file.

A code download does not export leads, email contacts, campaigns, replies, service-key values, or an entire account. Keep separate records where required.

03

Run and build the downloaded project

Follow the generated README and the versions in package.json. Install the dependencies before starting the local development server.

  1. Inspect every page at the local address.
  2. Run the production build.
  3. Test the production server and dynamic post pages.
  4. Deploy with a host that supports the exported project.
Run inside the extracted project
pnpm install
pnpm dev

# After checking the local site, stop the dev server and build:
pnpm build
pnpm start

The older purchased-code guide's static out/ upload process does not automatically apply to this Next.js export.

04

Replace the hosted services before moving traffic

Launch forms post to /__wr/lead, which the standalone project does not provide. Add a server receiver or replace the form integration.

The code copy does not receive future post or business-detail edits from Launch. Hosted analytics events need a replacement collector.

Environment-variable requests depend on Launch's secure service. Configure and implement an equivalent server integration on the new host; never expose the keys in browser code.

  1. Implement and verify the form receiver and visitor confirmation.
  2. Choose the future system for posts and business details.
  3. Preserve or migrate media before removing the original site.
  4. Configure analytics, redirects, security headers, and consent on the new host.
  5. Make a separate plan for customer email and its records.

Do not delete the original Launch site while the new deployment still depends on its media or business services.

05

Verify the migration before changing the domain

A successful build proves that the project compiles. It does not prove that customer-facing integrations work.

  1. Test the homepage, inner pages, posts, and not-found page.
  2. Submit a controlled form and confirm actual receipt.
  3. Test booking, payment, and service integrations separately.
  4. Check mobile layout, keyboard use, images, and old-address redirects.
  5. Move the domain only after the replacement passes the customer journey.
← All guides