Service · Software development

Platform migration with zero downtime.

The operational cut-over from an existing platform to a new stack, without your customers, employees or integrations noticing a thing. We carry out the migration, not just the advice. Strangler pattern, blue-green, CDC or database replication: we choose the migration path that fits your risk profile.

⇄

Migrating is an operation, not a presentation.

Replacing a platform sounds straightforward on paper: old stack out, new stack in. In practice, it is the execution that makes the difference between an invisible switch and a week of chaos in support, finance and sales. We specialise in that second part: the operational cut-over. Not the slide decks, not the lengthy consultancy story, but actually moving your platform without the business grinding to a halt.

Our role begins where the strategic story ends. Platform modernisation determines where you want to go; replacing legacy software is the broader decision-making process. Carrying out a platform migration is the phase that follows: actually moving data, integrations and users to the new system, with minimal risk to day-to-day operations.

We migrate CMS platforms, e-commerce stacks, CRM and ERP systems, databases, hosting environments and frameworks. Always with the same guiding question: how do we keep the shop open while we replace the foundations? The difference between a successful migration and an expensive failure rarely lies in the target architecture, which is usually well documented, but in the discipline with which data, integrations and user flows are monitored during the transition.

A good migration is largely invisible to end users. That is no coincidence, but the result of tight preparation: we first run the migration in full in staging, compare records by count and content, benchmark the performance of the new platform against the old baseline and keep a rollback path open until it is truly safe to proceed. The larger the platform, the more important that approach becomes.

The seven strategies we combine.

There is no single best way to migrate a platform. We combine seven established patterns depending on what the situation calls for. Martin Fowler's Strangler pattern, in which the new platform grows piece by piece alongside the old one until nothing of the legacy system remains, works well for large monolithic systems that we do not dare to pull apart in one go. Blue-green deployment creates a complete copy of the production environment and switches over via DNS or a load balancer, ideal for situations where a fast rollback is crucial.

For customer-facing platforms we often use canary releases: a small percentage of traffic goes to the new stack, and if the metrics hold up we scale up. Database dual-writes and Change Data Capture (CDC) keep the data in both systems in sync during the transition period, so there is never a hard cut-over moment when everything has to work at once. Read-replica failover first runs the same data as read-only on the new stack, which later becomes the primary. And feature flags let us migrate individual features rather than the whole platform at once.

Which pattern, or combination of patterns, suits your situation emerges during the discovery phase. We don't push a preferred pattern; the choice depends on data volume, integration complexity, downtime tolerance and how easily your legacy environment can be decoupled. For cloud-native platform development projects we more often choose canary strategies; in CRM and ERP migrations, CDC with dual-writes dominates.

What a zero-downtime migration means in practice.

Dual-write
Writing to both old and new during the transition
CDC
Real-time data sync via Change Data Capture
Rollback
Back to the old stack up to the last moment
Dry run
A full migration in staging before the real cut-over

Three types of migration we carry out.

Every migration has its own risk profile. The critical question is always: what is allowed to break, and what absolutely is not.

Option 01

CMS and content platform migration

Webflow, WordPress → headless

Migration from traditional CMS platforms to headless solutions such as Sanity, Contentful, Strapi, Payload or Directus. This includes content modelling, URL restructuring, redirects, SEO preservation and phased migration per page group. Often combined with a new frontend in Next.js or Astro. We make sure your existing organic rankings are preserved through careful 301 redirect mapping, canonical management and keeping metadata in sync during the transition. For publishers and marketing teams who have built up years of content, this is the migration type with the biggest SEO impact.

SanityContentfulStrapiPayloadDirectus301 redirects
Option 02

E-commerce, CRM and ERP migration

Business-critical, with integrations

Magento 1 or 2 to Shopify, commercetools or BigCommerce. Salesforce ↔ HubSpot, or a legacy CRM to a modern alternative. ERP projects such as Exact Globe → Exact Online or SAP ECC → S/4HANA. Here everything revolves around data integrity, integrations with third-party systems and carrying over open orders, invoices and customer data. We build a sync layer between the old and new environments so that orders arriving in the old system on day X are already in the new one automatically on day Y, without finance or customer service noticing the transition at all.

MagentoShopifySalesforceHubSpotExact OnlineSAP
Option 03

Infrastructure, database and framework migration

Under the hood

On-prem to cloud, or cloud to cloud (AWS ↔ GCP ↔ Azure ↔ Hetzner). Database migrations such as Oracle → PostgreSQL or SQL Server → managed RDS. Framework switches such as AngularJS → React, jQuery → a modern stack, or even Cobol/Delphi → a current foundation. Often invisible to end users, but decisive for maintainability, hosting costs and how quickly you can add features in future. For database migrations, the combination of logical replication and read-replica failover is our standard recipe: the new database first follows along as a replica, then gradually takes over write traffic.

AWSGCPAzurePostgreSQLReactTerraform

What you get after a successful migration.

Not just a working new platform, but also all the artefacts you need to phase out the old stack calmly.

New platform live

Production and staging, fully set up and performance-tested against the old baseline.

Migration report

Which data was moved, which records were exceptions, and how they were resolved.

Runbook and rollback

Documentation for IT to run both stacks side by side until the old one is phased out.

Audit trail data

For compliance: proof that data was transferred one-to-one, with checksums.

Decommissioning plan

Plan for phasing out the old platform, including data retention.

When an executed migration is the right choice.

Four patterns in which organisations come to us for the operational side of a platform transition.

Risk profile

The cut-over must not be visible

Your customers or staff use the system every day. A maintenance weekend with error pages is not an option because it directly affects revenue, NPS or operational continuity. In that case we choose a strangler pattern or dual-write until the new system fully takes over, with a rollback path that stays open until the last moment.

Data volume

Too much data to transfer in one go

Millions of records and years of history, linked to invoices, contracts or customer files. A naive export-import takes too long, breaks foreign keys and gives no consistent point-in-time snapshot. Here we use Change Data Capture to synchronise the data live with minimal load on the old system.

Integrations

Many third-party integrations

APIs that push to your platform, ERP integrations, payment gateways, BI tools that pull reports. These cannot all be switched at once, especially when external parties have their own release calendars. We facilitate running in parallel until each integration can switch individually.

Compliance

The audit trail is non-negotiable

Financial institutions, healthcare, government: you must be able to show which data was moved, when, and with which transformations. We deliver checksums per table, comparison reports, complete data lineage from old to new and documentation suitable for an external audit.

The six concerns we address as standard.

Every organisation considering a platform migration has the same categories of concern. We make them explicit and ensure that a concrete mitigation is on the table for each one before the cut-over takes place.

Downtime: we reduce this to zero by using blue-green, strangler or canary deployments instead of a hard cut-over moment. Data loss: we run a full dry run in staging plus checksumming at row and column level, followed by a post-migration verification report. Loss of functionality: we document what the old system actually does, which is often not the same as what the documentation says, and verify it feature by feature in the new one. Performance regression: we benchmark the old and new stacks against the same workload, and only go live once the new one performs at least as well. Rollback option: we never work with a hard point of no return; until the old system is decommissioned, falling back remains possible. Compliance: audit trail, GDPR compliance and data retention are not arranged ad hoc but are part of the migration design from day one.

How a migration project runs.

Our approach is divided into eight phases that flow into one another. Discovery, architecture, dry run and cut-over are the main milestones; in between are smaller steps in which we set up the sync layer, verification and monitoring. No migration skips a phase, even if the client says everything is already documented, because the dark integrations almost always only surface during discovery.

01Discovery→ 02Architecture→ 03Dry run→ 04Cut-over
Discovery

Discovery

Which systems are running, which data, which integrations, which dependencies. Including mapping out dark integrations.

Architecture and sync layer

Target-state design

Choosing the migration path: strangler, blue-green or CDC. Setting up a sync layer so the old and new stacks can run side by side for a while.

Full test

Dry run in staging

A complete migration in a staging environment. Verifying data consistency, benchmarking performance before and after, and testing the rollback.

Cut-over + monitoring

Go-live + decommissioning

DNS switch or traffic shift. Extra alertness for anomalies in the first period. The old stack is only switched off once everything is running stably.

Techniques and tools for zero-downtime migration.

We don't work from a single dogma. For each migration, we look at which combination of patterns carries the lowest risk for your situation.

Migration patterns
Strangler FigBlue-greenCanary releaseDual-writeRead-replica failoverFeature flags
Data sync
Debezium CDCKafka ConnectAWS DMSGCP DatastreamLogical replication
Infrastructure
TerraformKubernetesDockerCloudflarePostgreSQLRedis

Frequently asked questions about platform migration.

Can you really guarantee zero downtime?
No migration comes with an ironclad guarantee, and we only take on clients where zero downtime is realistic. What we do is apply every technical pattern available to bring downtime down to zero, run a dry run in staging so we know exactly what will happen during the real cut-over, and keep a rollback path open until the last moment. In practice, well-prepared projects end in a switchover nobody notices.
How can we be sure we won't lose any data?
Through three layers of verification. First, a dry run in which we carry out the full migration in staging and compare all records by count, checksum and sample. Then a sync layer (dual-write or CDC) that ensures everything arriving in the old system during the transition also ends up in the new one. Finally, a post-migration audit report that demonstrates, table by table, that the data has been transferred one-to-one.
What if something still goes wrong after the cut-over?
Then we roll back. For us, rollback isn't a theoretical concept but a tested procedure. During a blue-green migration, the old stack keeps running until we're certain the new one is stable, and switching DNS back takes minutes. With dual-write, both systems stay in sync for as long as needed. Only once we've seen no anomalies for several days do we phase out the old platform.
What do you do with our existing integrations?
We take stock, map out what can be carried over one-to-one and what needs adapting, and then run them in parallel for as long as necessary. We don't move third-party integrations (ERP, payment gateways, BI tools) over all at once. We build a sync layer between old and new so that each integration can switch individually when it is safe to do so. Also read our page on smart API integrations to see how we approach interfaces.
How long does a migration project take?
That depends heavily on the volume of data, the number of integrations and how well the old environment is documented. A CMS migration to headless often takes just a few sprints. An ERP or e-commerce platform with deep integrations is a project of several sprints, partly in parallel with building the new platform. In the discovery phase, we give you a reliable plan based on what we actually find, not on a first impression.
What determines the cost of a platform migration?
The biggest cost factor is the complexity of the existing environment: how much custom work, how many integrations, how well documented. Beyond that, the volume of data (for CDC setup and sync-layer performance), the number of compliance requirements (audit trail, retention, GDPR) and whether we also add new functionality during the migration or do a pure lift-and-shift. We never give a price based on the proposal alone; only after a discovery do we know what is really going on.
Do you also handle just the execution, or do I have to take the whole engagement?
Either works. Some clients already have the strategy settled, often with an in-house architect or through a platform modernisation engagement, and just want someone to carry out the migration technically. Others come in earlier, together with replacing legacy software as a broader review. Both are welcome; we're flexible about which part of the chain we take on.

Talk to us about your platform migration.

A no-obligation half-hour introduction. We listen to your situation, your current stack, the target state you want and the risks you see yourself. Afterwards we can tell you honestly whether zero downtime is realistic in your case and which migration path fits. For broader platform engagements, we also point you to our pages on cloud-native platform development and enterprise software development.

If your website is moving to the new platform too, read about SEO for a website migration.

Edit content