Discuss this project

We agree scope and fees before work begins.

What we deliver

A defined scope, ready for handover

Generated files and published pages

Compare available project files with the published site, approved content and assets. Establish what can be reused and what needs rebuilding before estimating the move.

Sites features and connected apps

Inventory sign-in, stored data, forms and connected-app access. Agree replacement services and permissions; ChatGPT workspace access is not assumed to carry over to a new website.

Editable Webflow pages

Rebuild approved layouts as responsive components and CMS templates. Connect the agreed forms and keep application-only features in the service chosen during discovery.

URL mapping and launch checks

Inventory existing URLs and metadata, preserve suitable paths and map changed URLs to relevant destinations. Test redirects, internal links, forms, analytics and indexability before and after the switch.

How we work

Agree, implement, verify

  1. Define the scope

    Review the current setup and agree deliverables, responsibilities, access and acceptance criteria before implementation.

  2. Build and review

    Work through representative examples, share progress and resolve issues against the agreed criteria.

  3. Launch and hand over

    Complete the agreed checks, document known limitations and hand over ownership, instructions and any separately agreed support.

Scope & responsibilities

The estimate depends on templates, content volume, languages, integrations and design changes. Platform subscriptions and third-party services are separate. Migration can cause search visibility fluctuations; preserving rankings or traffic is not guaranteed. We agree a launch checklist and a monitoring period.

What to share for an estimate

Share the preview or published URL, available code and assets, and the Sites features or connected apps in use. With a preview alone, we first assess a rebuild.

Discuss this project

Questions before you start

Plan the work with clear expectations

Does this cover ChatGPT Sites / GPTSites as well as generated code?

Yes. We assess published ChatGPT Sites and website code created in ChatGPT. A public link does not establish access to source files, private data or connected services, so the transfer method is agreed after review.

Can you preserve our search traffic?

We plan URL mappings, redirects, metadata and internal links to reduce avoidable disruption. Search engines need to process changes, so stable rankings and traffic cannot be guaranteed.