Newstools for publishers
CMS migrations and integration
Change CMS, domain, or architecture without losing visibility or control over what gets published.
Let's talk about your project
Frozen baseline
Inventory of URLs, templates, sitemaps, and traffic per brand before each cutover.
Tests before the cutover
URL mappings, redirect rules, and acceptance cases per template.
Connectors under control
States, retries, and a record of what was sent so nothing gets published by surprise.
From baseline to cutover
A person decides at this step
- Inventory and baselineURLs, templates, sitemaps, traffic, and internal links per brand, cross-checked with crawls and Search Console.
- Mappings and rulesWe define the URL map, the redirect rules, and the connectors between systems.
- Acceptance testsCases per template and per brand: we check redirects, canonicals, hreflang, and business-critical pages.
- Cutover approvalYour team reviews the results and decides when each brand migrates.
- Cutover and monitoringWe run the change in the agreed window and track indexing, HTTP responses, and structured data.
- Before-and-after comparisonA log of traceable issues and dated follow-up to separate real changes from noise.
No brand changes systems without approved tests.
What it solves
An editorial migration touches the CMS, the domains, the templates, and the teams at the same time. Each brand has its own URLs, sitemaps, and publishing windows, and a redirect that goes wrong in one template multiplies across thousands of pages. The risk is not only technical: it is losing organic visibility right when nobody can watch it because everyone is focused on the cutover.
The same problem shows up without a migration when content has to flow between systems: external sources, newsroom tools, queues, webhooks, and publishing platforms. If the connectors do not control states, retries, and duplicates, unexpected publications appear and nobody knows what was sent.
How we work
Before each cutover we freeze a baseline: we inventory URLs, templates, sitemaps, traffic, and internal links by brand, and we cross-check sitemaps, crawls, and Search Console. On that baseline we define URL mappings, redirect rules, and acceptance tests per template.
After launch we monitor indexing, HTTP responses, canonicals, hreflang, structured data, and business-critical pages, and we compare before and after by date to tell real changes from noise. We coordinate engineering, SEO, product, and editorial teams around traceable issues and shared priorities, and we adapt the plan to each group's CMS, publishing windows, and resources.
For integrations we build connectors and automations with API contracts, job states, retries, and observability. We adapt fields, taxonomies, media, and publishing rules to the destination system, and exports can be conditioned on quality checks and editorial approval.
What we deliver
- Inventory and baseline per brand, with URL mappings and redirect rules.
- Acceptance tests per template and a cutover plan with owners.
- Post-launch monitoring and a log of verifiable issues with dated follow-up.
- Connectors with failure recovery and a record of what was sent, to prevent duplicates and unexpected publications.
Who it is for
Publishing groups changing CMS, unifying domains, or reorganizing their architecture with several brands, languages, and teams involved. And newsrooms that need sources, tools, and CMS platforms to talk to each other without editorial control getting lost along the way.
What we have already built
Connectors and experience with WordPress, Strapi, Airtable, webhooks, and n8n, with API contracts, job states, retries, and observability. We use them as the starting point for each integration and adapt them to your CMS and your publishing rules.