Home · Platform · Platform · Migration
Bring your site across, page by page.
The expensive part of every re-platforming project is the same: a person, re-placing content into the new system, page after page, for months. Noice.work makes that step the agent's job. Give it the address of any page on the public web and it comes across as a reviewable draft — re-authored into your components, wearing your brand, with the source page's own images imported alongside.
What the importer keeps, and what it refuses
The read keeps what the page says — headings, prose, lists, quotes, calls to action — and deliberately discards its markup, because importing markup imports every problem the markup had. Images are copied into your media library through the ordinary import path, with provenance recorded, size caps enforced and duplicates detected. The re-authoring is offered only the images just imported and told to invent nothing the source does not carry. The shared header and footer of a site come across the same way, recreated from the read's own outline of them.
Everything arrives as drafts behind your normal review gates. Nothing an import does is live until a person publishes it.
The cutover machinery
Redirects are a single authoritative manifest — bulk-imported from CSV, validated as a whole graph before an atomic commit, with scheduled activation for campaign cutovers. Publishing is an immutable release, so a section cutover is a pointer flip and reversing it is the same flip. And because there is no build step, migrating incrementally is the natural shape: a section at a time, each reviewed, published and repointed on its own schedule.
The CMS migration guide covers the whole project shape — inventory, URL mapping, SEO preservation and the checklist we use ourselves.
Questions people ask
What can it read?
Anything that serves public HTML — WordPress, AEM, Sitecore, Drupal, Webflow, static sites. Reads are security-bounded and rate-respectful. Content behind authentication moves via export instead.
Does the brand migrate too?
Yes — the brand engine reads your existing site's real rendered styles and generates the design language your migrated pages wear. See the brand engine.