Skip to content
Services

CMS migration

Content moved between platforms with AI-assisted tooling, a redirect for every URL and a budget set in discovery.

Book a scoping callSee case studies
01 / What you get

How a Noice migration is different

We built our own tooling for migration and a method around it, instead of staffing a bench against a spreadsheet.

AI-assisted content move

Our migration tooling crawls the source, infers content shape, and writes into the target platform's management API. Editorial approves in batches; nobody re-keys 2,000 pages.

SEO continuity

A redirect for every URL, checked before cutover. Server-rendered target, structured-data parity, and Search Console + GA4 watch through warm-up.

Platform-agnostic advice

Magnolia Platinum Partner, but we migrate to whatever fits: headless, Drupal, bespoke. We are not paid by platform vendors and will say no to a bad fit.

Discovery with a fixed envelope

Two to four weeks of discovery produces a content inventory, integration map and a budget envelope you see before committing to the build.

Content triage, not bulk copy

Most estates carry content worth retiring. You pay to move the content that earns its place, not the 2014 campaign pages.

The build team stays on

The team that builds your platform supports it after go-live, with agreed response times by severity.

02 / Migration tooling

CMS migration tools

We automate the content move with our own AI-assisted tooling, so a migration is a supervised run instead of months of copy and paste. It works with sources including AEM, Sitecore, Optimizely, OpenText TeamSite, Drupal and WordPress, and writes into Magnolia, headless platforms and other targets through their management APIs.

Content capture

Captures every page from the source site with its images, documents and metadata, so the migration works from a complete picture of the estate.

Field and component mapping

AI infers the content shape and proposes a template, component and field mapping into the target model. Your team approves the mapping before any content moves.

API-driven content transfer

Pages, content items and assets are written into the target through its management API. No copy and paste, no manual uploads.

Links and assets intact

Internal links are remapped to the new site structure, external links are preserved, and images and documents move into the target DAM.

Content enrichment

Alt text, meta descriptions and structured data are generated where the source is missing them, for editors to review.

Approval in batches

Editors review and approve in batches, with coverage tracked by section, brand or region. Nothing goes live unreviewed.

03 / Consolidation

Consolidation

For organisations merging sites, retiring brands or leaving an ageing platform. AI reads every site in scope; your people make every decision.

A fixed-price discovery sprint

Two to four weeks across your estates, quoted at a stated page and asset ceiling. It produces a full content inventory, an overlap matrix, a keep, merge, rewrite or retire call for every page, a register of regulated content and a gap analysis, presented at a readout for each audience. You keep everything it produces, whoever does the build, and the migration is priced from its real counts.

Book a scoping call →
ProofAll case studies
National Cancer Screening Register case study

National Cancer Screening Register / UX Research / Design Systems

Enterprise UX transformation & managed AEM support

A complete redesign with improved UX, a new design system, and ongoing managed support.

Read the case study →

Free resource

Get the CMS migration checklist

Every pre-flight, in-flight and post-launch check we run on real enterprise migrations. Five phases, printable, free.

One email with the link. No drip sequence, no spam.

04 / Questions

CMS migration: FAQ

The questions Australian teams ask before committing to a migration.

Costs vary widely with the scope and complexity of the project. In the Australian market in 2026, a focused single-site migration with a kept frontend typically comes in under AUD 100k, while multi-site enterprise estates with a frontend rebuild commonly run several times that. The biggest drivers are whether the frontend is kept or rebuilt, the size of the estate, and how much content transformation the move requires. We share an itemised range at the end of a one-hour scoping call, and discovery produces a fixed budget envelope before you commit to a build.

A typical Australian mid-market migration (one brand, 500 to 2,000 pages, a handful of integrations) runs twelve to twenty-two weeks end to end. The two biggest variables are whether the frontend is rebuilt at the same time and how much content transformation the move requires. Discovery gives you a dated plan, not a guess.

Not if continuity is treated as a release blocker, which is how we run it: a 301 redirect map for every URL, server-rendered HTML on the target, structured data parity, sitemap re-submission, and daily Search Console plus GA4 monitoring through the warm-up window. Some ranking turbulence in the first weeks is normal; permanent loss means something was skipped.

From: AEM, Sitecore, OpenText TeamSite, Drupal, WordPress, Squiz Matrix, Kentico, legacy and bespoke systems. To: Magnolia (we are a Platinum Partner), headless platforms like Contentful, Contentstack, Sanity and Strapi, Drupal and GovCMS alternatives, and modern bespoke stacks. We are platform-agnostic outside the Magnolia partnership and will tell you when a platform is the wrong fit.

Our own AI-assisted migration tooling. It crawls the source CMS, infers the content shape, maps templates, components and fields to the target model, and writes content and assets into the target platform through its management API, with editorial approval in batches. It typically removes most of the manual content-loading effort. It is part of how we deliver, not a separate licence, and for unusual targets we build a custom writer during the engagement.

Less than you think. Most estates carry content worth retiring: duplicate pages, expired campaigns, orphaned assets. We classify everything as migrate as-is, transform, rewrite or retire during planning, so you pay to move only the content that earns its place.

Yes. The approach is the same five stages, with extra care on extraction since vendor support and documentation are usually gone. The longer an EOL platform runs, the higher the security and extraction risk, so earlier is cheaper.

Yes. Our case studies include the NCSR redesign and the Collaborative Centre's 6.4 upgrade.