Arc XP to WordPress VIP Migration
Your publication ships every day on a closed platform built inside another publisher. Moving to WordPress VIP means moving every story, gallery, video, author and URL, with your integrations accounted for and the newsroom publishing until cutover day.
The real problem
Stories go out and the site holds. What slows you down is that every new tool, from the paywall to the image library, depends on the catalog of a vendor that is also a publisher.
On Arc XP you pay per product used or for the full platform, and stories, galleries and home pages live in separate tools: Composer, Photo Center, Video Center and PageBuilder.
Still weighing the platforms? Compare WordPress VIP and Arc XP.
What the migration covers
A migration is not a content export. These are the six layers that decide whether the new site behaves like the old one on launch day.
Stories and content model
Arc XP stores content in ANS: stories, galleries and videos with their elements. Each type and field is mapped to WordPress post types, fields and taxonomies in the diagnosis, so every story lands where the newsroom expects it.
Home pages and layouts
Pages built in PageBuilder become blocks and patterns editors place themselves, in the same editor where they write the story.
Images and video
Photo Center images and videos import with their credits and alt text, with duplicates removed. A second pass rewrites every reference inside stories, so nothing breaks after launch.
URLs and redirects
Every URL search engines know is captured with a full crawl of the site. The redirect map is built from that crawl, and one rule holds: no redirect chains.
Integrations
Subscriptions, paywall, newsletters, advertising and analytics are reviewed one by one in the diagnosis: connected to the tool you choose, rebuilt or retired, and tested before the switch.
Authors, sections and roles
Authors, sections and tags come across with their URLs. Users and their permissions map onto WordPress roles, with each author kept on their stories.
What changes
After the migration, the newsroom writes, builds and publishes in one place, and chooses every tool around it.
Editors write the story and build the home page in the same block editor. Paywall, images and analytics connect to the tool you prefer, and changing one no longer depends on the vendor. Your developers go back to work that needs developers.
Not Arc XP, but the same problem: Plant Based News needed a site that holds up when a story goes viral, with editors who publish without code. Read the case
The plan
Three steps, with a decision point at the end of each one. Your Arc XP site keeps publishing until the new one is verified.
A full crawl of the site, an inventory of the archive and content types, an integration review and a baseline of every URL, canonical tag and metadata value. Then a pilot: a real slice of the archive migrated end to end, so the mapping is proven before the full run.
Frontend, backend and archive migration run in parallel while the newsroom keeps publishing on Arc XP. QA covers browsers, integrations, traffic peaks and the editorial workflows, tested with the people who will use the CMS.
Cutover with the previous platform kept available, so rollback is a decision rather than a project. We watch rankings and coverage until they settle, and keep improving the platform with your team.
Before you commit
In 30 minutes we look at your site, your archive and your integrations, and tell you what a move to WordPress VIP involves. No obligation to go further.
FAQ
The questions teams ask before they decide, answered plainly.
Ready when you are
Bring us your Arc XP site and we will map the path to WordPress VIP: archive, redirects, integrations, brands, and the workflows your newsroom will use on day one.
