Trusted by some of the world’s leading brands
Sounds familiar?
If you’re on Arc XP, none of this will surprise you.
Your pricing tier scaled up when traffic grew, but the platform’s capabilities didn’t change.
Hiring is slow and expensive, as there are only 3 Arc XP Gold Partners globally.
Arc XP has gone through multiple rounds of layoffs. Your platform roadmap depends on a team that keeps getting smaller.
Documentation can be inconsistent, which slows onboarding and makes ramp-up harder for new engineers.
Most implementations rely on custom development, so even small changes take time and slow down delivery.
Leaving Arc XP resolves most risks.But a poor migration can create new ones
Rushed execution can undo years of work: your rankings, your content structure, and your editorial workflows. Our Arc XP to WordPress migration services are designed to protect all three.
SEO performance
Arc XP SEO depends on syndication feeds, large-scale sitemaps, and cross-brand canonical logic. If not rebuilt correctly, rankings drop even when content and URLs stay the same.
How we prevent SEO deterioration
We audit every URL, feed, and sitemap before migration begins. Canonical logic is preserved across brands. We run full crawl simulations before launch to protect your rankings.
Content integrity
Arc XP content spans Composer, Photo Center, Video Center, and custom models, all tied together through a proprietary data model. Without structured mapping, content relationships fall apart.
How we prevent content loss
Composer content, media assets, and custom types are mapped field-by-field. All relationships are preserved, and every content object is validated before go-live.
Team productivity
Arc XP’s editorial tools are built for Washington Post-scale newsrooms, so they’re often over-engineered for smaller teams. A bad migration can carry that same complexity into WordPress.
How we prevent adoption failure
We redesign Arc XP workflows around how your team works. Gutenberg replaces complexity with reusable components, so your editorial team can update content without developer support.
Moving three independent publications ontoa single WordPress VIP multisite with zero data loss
This standardized approach has allowed us to roughly halve our ongoing development costs and achieve higher code quality, all while making progress on our roadmap quicker than ever before.
Kevin Cooper
Chief Growth Officer
Your platform vendor competes with you…and you’re funding it
Here are the Arc XP trade-offs you don’t notice until you’re already locked in.
 Arc XP |  WordPress | |
|---|---|---|
| Annual platform cost | $100K–$4M+ annually. Usage-based pricing scales with traffic. Your CMS gets more expensive as your traffic grows. | 2–3× lower at comparable scale. No per-seat pricing and traffic-based tiers. |
| Vendor stability | Three rounds of layoffs in 18 months. Its parent company, The Washington Post, lost $77M in 2023 itself. | WordPress runs 43% of the web. It’s backed by Automattic and a large global community, so no single company controls it. |
| Vendor conflict | The Washington Post licenses Arc XP to publishers, then competes with those publishers for readers, advertisers, and subscribers. | No competing interests. Your infrastructure vendor does not also run a newsroom. |
| Editorial tools | Designed for enterprise-scale newsrooms, not for everyday publishing teams. | Gutenberg gives editors a block-based visual editor they can operate without developer tickets. |
| Talent availability | Specialist developers are niche, expensive, and hard to find. | 500,000+ developers globally. |
| Ownership | SaaS. You own no code. Infrastructure decisions are made by Arc XP. | Full open-source ownership. Every line of custom code is yours. |
Arc XP gets more expensive as you grow. WordPress gives you control over how your costs scale.
Why WordPress is the strategic exit
When you leave Arc XP, you take your content and nothing else. On WordPress, the infrastructure decisions are yours, and no vendor can reprice, restructure, or shut down what you’ve built.
Owned infrastructure
No licensing fees. Your codebase is yours. Fork it, extend it, or switch partners without starting over.
Editorial independence
Gutenberg lets editorial teams control layouts, add media, and publish without developer support.
Composable architecture
Pick the analytics, ad tech, CRM, and personalization tools that fit your operation. No bundled ecosystem forcing your decision.
The largest talent pool in CMS
50,000+ WordPress developers globally, so finding one who understands your platform is never a constraint.
How we migrate from Arc XP to WordPress
Arc XP migrations demand structured engineering, so we follow a phased approach to reduce risk at every step. All engagements start with 20 hours of free discovery.
Migrate fromArc XP to WordPress
Your critical assets, fully protected
Every migration introduces risk. We plan for all of it.
SEO equity preserved
Your rankings carry over across every URL
We audit every URL, validate redirect chains, check metadata field by field, and run full crawl simulations to ensure nothing breaks at the switch.
Content integrity validated
Your content arrives complete and usable
We break migration down at the field level, map taxonomy and media relationships, and validate everything through checkpoints across the process.
Editorial workflows rebuilt
Your team publishes without friction
Editorial workflows are rebuilt around your team’s needs. Gutenberg components replace rigid templates, so publishing is faster and more intuitive.
Integrations maintained
Your existing tools continue to work as expected
Paywall, ad tech, analytics, syndication feeds, and video partnerships are rebuilt and tested against production traffic before go-live.
Zero downtime deployment
Your site goes live without disruption
The new platform is developed alongside your existing Arc XP setup. Deployment follows a blue-green approach with instant rollback available.
Team enablement included
Your team runs the platform on its own
Once live, your team is equipped with documentation, hands-on training, and 30 days of dedicated Hypercare support.
Why choosertCamp as your Arc XP to WordPress migration company
We’ve delivered 300+ enterprise WordPress migrations, including large-scale publisher platforms.
Known for complex WordPress migrations
We built Grist’s award-winning journalism tools on WordPress VIP and helped Private Media unify three publications, cutting development costs by 50%.
We’ll tell you if you don’t need us
If staying on Arc XP and negotiating your contract makes more sense than migrating, we’ll say so. We don’t push migrations that don’t add up.
WordPress VIP Gold agency
Core contributors for 34 consecutive WordPress releases. 200+ engineers in-house. SOC 2 compliant. 96% client repeat rate.
Why enterprises trust rtCamp
What ourclients say
We started off young, back in 2011, with an idea that evolved into a big company.
This standardized approach has allowed us to roughly halve our ongoing development costs and achieve higher code quality, all while making progress on our roadmap quicker than ever before.
We’ve been very impressed with the flexibility and expertise of rtCamp’s team, who implement a wide range of website features and functionalities for us. Their work continues to add so much value to our articles and award-winning special features. We’ve also been thankful to rtCamp for consistently being available and on point for last-minute projects and tasks.
Planning to move from Arc XP to WordPress?
BWe’ll assess your setup and recommend the right path, be it WordPress or something else.
Check outour resources
Handbook
Arc XP vs WordPress comparison guide
Handbook
Arc XP to WordPress migration guide
case study
Grist case study
Frequently asked questions
Most migrations take 3–6 months from discovery to launch, depending on content volume, integration complexity, and the number of brands involved. The discovery phase, which you start with 20 hours at no cost when working with us, will get you a detailed roadmap with timeline and budget before development begins. Multi-brand publisher migrations typically run 6–9 months.
No, if the migration is engineered correctly. Every Arc XP URL is mapped before migration begins. Canonical signals, XML sitemaps, and internal linking architecture all transfer to your WordPress environment. We run automated validation against your live site to catch gaps before launch.
Paywalls, ad tech, analytics, syndication feeds, and video partnerships all connect to WordPress through established integration patterns. We’ve rebuilt these across dozens of publisher environments. The integration rebuild is a dedicated phase of the migration, and all connections are tested against production traffic before go-live.
WebSked is Arc XP’s editorial planning and scheduling tool. During discovery, we document your current WebSked workflows, like scheduling cadence, contributor roles, approval chains, publication rules, and map each to an equivalent WordPress workflow. We build the tools your editorial team needs, not a generic replacement.
Composer article types map to WordPress custom post types. Photo Center and Video Center migrate to WordPress’s centralized media library with bulk operations, focal point cropping, native video embeds, and custom gallery blocks. Multi-brand publishers get a shared Content Hub that centralizes assets across properties.
We have migrated enterprise publishers from AEM, Sitecore, Kentico, Drupal, .NET, and custom CMSs. These platforms feature exact characteristics that make Arc XP complex, like proprietary content models, enterprise-scale content volumes, deeply embedded integrations, and zero tolerance for downtime. We worked with Al Jazeera, PMC (parent of Rolling Stones, Hollywood Reporter), and Grist on editorial WordPress platforms at newsroom scale. The engineering patterns are the same.
That’s what our free consultation is for. We’ll assess your current setup, costs, and risks, and recommend the right approach, even if it’s not WordPress.
Look at their enterprise CMS migration track record. Check whether they hold WordPress VIP partnership status. Ask how they handle field-level content mapping and media migration, and confirm that they provide dedicated post-launch support.