ANODA Discuss your product

Website Migration & Replatforming

ANODA moves your content, templates and integrations to a platform your team can run, preserving earning pages and rehearsing recovery so growth stops depending on platform workarounds.

Discuss your migration Explore our work
A steel robotic arm on a gantry carries an orange block from an old white ceramic page frame to the matching slot in a new one.
Custom scope
Fixed or phased, set in the proposal
Every URL accounted for
Mapped before anything moves
Old site kept restorable
Until you sign off the switch
Timeline agreed
After scope, access and dependencies

In short

Your site on a new platform, with its content, URLs and forms carried across.

What's included

  • Source audit
  • Content model
  • Rebuild
  • Redirects
  • Integrations
  • Cutover

Answers you'll have before anything moves

  • Is moving worth it at all?
  • Which platform should the site move to?
  • What moves as it is, and what is rebuilt?

Where it stops

Website Redesign

Reworks the site's structure, pages and look.

Website Migration & Replatforming

Moves the site you have to a platform that suits it.

Not included

  • A redesign or new copy unless separately scoped
  • Platform, hosting or third-party fees

Everything the old site did, accounted for on the new one

What you walk away with, from the site inventory to the cutover runbook.

Discuss your migration
  • A white ceramic tray of labelled index cards sorted into rows, one card graphite, a steel tag lying beside it.

    Migration inventory

    Every URL, content type, form, script and integration, each with its fate.
  • A ceramic base plate with three stacks of tiles joined by thin steel rods to one small tile, one stack capped in graphite.

    Platform choice and content model

    The new platform, how content is structured in it, and who edits what.
  • Two ceramic browser windows, one rough and one clean, joined by a thin steel rail carrying small blocks across, one graphite.

    The migrated site

    Templates rebuilt, content moved, and forms and tools reconnected.
  • A ceramic plate where one steel-railed track splits in two, a small steel lever with a graphite knob at the split.

    Redirect map and cutover runbook

    Old address to new, the switch steps, the checks, and the way back.

You receive

  • The live site on your accounts
  • Redirect map and test record
  • A runbook for your team

The old site keeps running until the new one has proved itself.

A new platform does not repair an unlisted lead form or preserve a URL nobody mapped. ANODA inventories the live journeys first, picks the destination around your editors and integrations, and carries the page, content and action across together. The result is a working site your team can publish on, with a clear way through the switch.

  • Inventory

    The old site crawled and its exports read: every URL, template, content type, form, script and integration, and which pages earn visits and links. Needs Admin access to the current platform, analytics and search console.

    Done when Every URL and function has a verdict — move, rebuild, merge or retire — that you have approved.

  • Platform and model

    Candidate platforms weighed against how your team edits, what the site connects to and what it costs to run; the content model drawn for the chosen one. Needs Who edits, how often, and which tools must stay connected.

    Done when You approve the chosen platform, the content model drawn for it and who edits what, in writing.

  • Foundation and templates

    Shared components first, then one template at a time with its real content, compared page by page with the old site on staging. Needs A staging environment or a seat on the new platform.

    Done when Each template carries the old page's content, headings and metadata, passes keyboard and contrast checks, and meets the agreed speed budget.

  • Content and connections

    Content moved by script where the export allows and by hand where it does not; forms, analytics and tools reconnected and tested with controlled submissions through the agreed destinations. Needs Test accounts or sandbox access for each connected tool.

    Done when Content counts reconcile with approved moves, merges and retirements, media resolves, and every form reaches the right inbox or tool.

  • Cutover

    Redirects loaded and tested, a content freeze agreed, the domain switched in a quiet window, then errors, redirects and search coverage watched. Needs Access to the domain's DNS, a quiet window with content frozen, and one decision-maker for go or no-go.

    Done when Each old URL has its approved outcome: retained page, one-hop relevant redirect or intentional retirement. Alerts reach an owner; recovery protects new form submissions and content changes as well as the previous site.

  • Handover

    The runbook, redirect map and test record handed over, and editors walked through the new workflow. Needs The people who will edit and run the site.

    Done when Your team publishes a change on its own and knows who to call for what.

Who owns what

ANODA builds

  • The audit of URLs, templates, content, forms and scripts
  • The platform comparison and the new content model
  • Templates, components and the content transfer
  • Redirects, metadata, sitemaps and structured data
  • Forms, integrations and the cutover runbook

Your team owns

  • The platform decision, its plan and its fees
  • Domain, DNS, hosting and email records
  • Analytics, search console, CRM and tool accounts
  • Content sign-off and the go-live call
  • Running the site after the handover

Platforms and tools provide

  • The old platform — its export tools, limits and contract end
  • The new platform or host, and its uptime
  • Search engines, which decide when to re-index the new URLs

When a website migration is the right step

It fits when the platform, not the message, holds the site back. Four signs it is the right step now.

  • Small edits need a developer

    A new page or a price change waits in a queue because the platform makes it risky.

  • The running cost has outgrown the site

    Plans, plugins, seats or hosting cost more each year while the site does the same job.

  • The platform blocks the next step

    Languages, speed, integrations or code your engineers must own are hard or impossible where you are.

  • The site already earns visits

    Search traffic, links and leads come in, and a careless move would throw them away.

A different starting point

Let's list what your site does before it moves

Tell us what the site runs on and why it has to move. We will come back with a useful scope and a realistic next step.

Discuss your product Explore our work

Scope, access and who does what

The pages, content types, integrations and the cutover window are agreed before anything moves.

Scope
Custom fixed or phased, set in the proposal
Timeline
Agreed after scope, access and dependencies
Discuss your migration

  1. You provide

    The site today
    Its address, the platform it runs on, and admin access or an export.
    Why it has to move
    The limit you hit: cost, editing, speed, a contract ending or a missing feature.
    What it feeds
    The forms, CRM, analytics, scripts and other tools connected to the site.
    One decision-maker
    Someone who approves the platform, the redirect map and the go-live.

  2. Who does what

    ANODA
    Audits the old site, plans and builds the new one, moves the content, runs the cutover and hands over.
    Your team
    Grants access, decides what moves, reviews each step and makes the go-live call.
    Your providers
    Keep the old platform, the new host and the domain running, and answer our technical questions during the move.

  3. Boundaries

    Outside a migration
    A new structure or look, copywriting, a new brand, paid media and SEO campaigns, and platform or third-party fees.
    After cutover
    Your team edits and runs the site. Support, fixes and a next phase are scoped separately.

Related services

What is your website running on today?

Tell us its address, the platform, why it has to move, and the tools it feeds.

What do you need? *
Project budget (USD) *

What is your product, who uses it, and what would you like us to do?

    Within 15 minutes, we’ll reply with initial feedback and follow-up questions.

    Read more about running a website

    All articles

    Website Migration & Replatforming: common questions

    What should we ask a team offering website migration services?

    Ask how they find out what the old site does before they build anything. A good answer names a crawl, the platform's exports, analytics and search console, and a written verdict for every URL and form. Ask to see a redirect map and a cutover runbook, who holds the rollback, and how they check the site in the days after the switch. Be wary of a team that is excited about the new platform and never asks about your old URLs.

    What do website replatforming services include?

    An inventory of the old site — URLs, templates, content types, forms, scripts and integrations — and a comparison of platforms against how your team works. Then the content model on the chosen platform, the rebuilt templates, the content transfer, forms and tools reconnected, redirects, metadata and sitemaps carried over, and a rehearsed cutover. It ends with a handover: the runbook, the redirect map, the test record and a walkthrough for your editors.

    Will we lose search traffic when the site moves?

    Missing pages, unmapped URL changes and accidental changes to titles or headings can reduce search traffic during a move. So every URL that earns visits or links gets a destination before the build, metadata and structured data are carried across, redirects are tested on staging, and errors and search coverage are watched after the switch. Search engines re-crawl a moved site in their own time, so positions can wobble for a while. Our post-switch checks identify migration errors so they can be fixed while the new platform settles in.

    Will the site go offline during the switch?

    It should not. The new site is built and checked on staging while the old one keeps serving visitors. The switch moves traffic to the new platform in an agreed window, with any DNS changes and URL redirects prepared and a content freeze in place. The old site stays restorable through the agreed recovery window. The plan also protects leads, content edits and integration activity created after cutover; switching DNS back alone does not reverse that data.

    Which platform should we move to?

    The one that suits the people who edit the site and the tools it must talk to. We compare the editing and approval workflow, content model, integrations, performance requirements and total running cost. Options can include Webflow, WordPress or a coded site such as Astro with a CMS; the choice follows your actual publishing tasks and the team that will maintain it. We compare the options in writing before anything is built.

    Should we migrate, redesign, or stay where we are?

    Stay when the platform still fits and the pain is elsewhere: a UX Audit will show where. Choose Website Redesign when the structure, pages and look need rework, whether or not the platform changes. Choose a migration when the platform itself is the limit and the site is worth keeping. If the site runs on Webflow, WordPress or Framer, the page for leaving that platform goes into the specifics.

    What do you need from us to start?

    The site's address and admin access to its platform, or a full export. Analytics and search console access, to find the pages that bring in traffic and links. A list of the forms, scripts and tools the site feeds, and the reason it has to move. Then one person who approves the platform, the redirect map and the go-live date, and access to the domain and DNS before cutover.

    What will we have at handover, and can you stay on afterwards?

    The live site on your own accounts, the migration inventory, the redirect map with its test record, the cutover runbook and a walkthrough for the people who edit and run the site. After cutover your team owns publishing. We can stay on for fixes and new pages, test the key paths with real visitors, or take on a redesign or a next phase, each scoped separately.

    What decides the scope, timeline and price?

    The number of URLs and templates, how many content types and items there are, how clean the old platform's export is, the forms, scripts and integrations to reconnect, whether languages or member areas are involved, and how many redirects the site needs. We set a custom scope and estimate in the proposal, fixed or phased, and agree the timeline once scope, access and dependencies are clear.

    What is not included, and what have you built before?

    A new structure or visual redesign, copywriting, a new brand, paid media and SEO campaigns, and platform, hosting or third-party fees, which stay in your accounts. Our easyStorage NL case shows a Webflow website and booking flow we designed and built. Your migration scope starts with the existing content and integrations, an approved URL map and acceptance checks for the new platform.