Skip to content

// ccm & migration practice

Migrating a CCM platform, all the way to shutdown

Modernising a legacy document platform without ever interrupting production.

Statements, renewal notices, contracts, invoices: a customer communication platform never stops. We migrate these platforms from the measurement of the estate through to the actual shutdown of the source platform, with proof of equivalence at every cutover.

// 01 · what we do

Four moves, from estate to cutover

A platform in production for fifteen or twenty years carries anything from a few hundred to several thousand document templates. Scale changes the size of the programme, never its method.

M1Measure the estate

A real inventory of templates, volumes produced over a rolling twelve months, dead templates, variants of the same document, business logic buried in the layouts. The study becomes a measurement, and the scope a figure.

M2Rationalise and converge

Merge redundant templates before migrating, especially after mergers of entities, then set up shared document governance that prevents them drifting apart again. Migrating an estate that has not been cleaned up just moves the debt.

M3Rebuild and prove

Analysis of the legacy sources, normalisation into a canonical model, tool-assisted generation for the target engine. Then automatic comparison of both chains’ output, document by document, against a definition of equivalence settled at the outset.

M4Cut over without interruption

Parallel running and flow-by-flow cutover. Annual flows are validated outside peak periods, on test sets derived from the previous year’s data, within a controlled GDPR framework. Through to the shutdown of the source, not just letting it go dormant.

// 02 · why now

What could not be costed now can be

For twenty years, shutting down a document platform was desirable in theory and unfundable in practice: nobody could say what it contained, what rebuilding it would cost, or how to prove the new chain would produce the same documents. Four obstacles have fallen together:

Article · in French

Décommissionner un socle CCM historique est devenu possible

Our founding article on decommissioning legacy CCM platforms: the four obstacles one by one, why migrating is above all about reopening a choice, and the first three steps before any major commitment. Currently available in French only.

// 03 · references

Programmes delivered over the long term

Public sector and large publishing organisations · Switzerland and Europe · 4 to 5 years

Decommissioning legacy platforms

Context
Legacy document platforms that had become hard to maintain: mainframe dependencies, bespoke unit processing, scarce skills.
Outcome
Legacy platforms fully decommissioned, no service interruption during migrations, and lower operating costs.

Insurance, social protection and pensions · France and Switzerland · 5 to 9 years

Converging multi-entity platforms

Context
Successive mergers, separate engines, thousands of redundant templates, several million documents a year in a regulated environment.
Outcome
Gradual unification on shared platforms, parallel-run migrations with no interruption, common document governance.

Document production and services · Switzerland · ongoing

Steering a multi-year programme

Context
Migration of several hundred document templates involving many stakeholders.
Outcome
A dedicated steering tool: schedule, workload and capacity indicators shared by every stakeholder, faster estimating and reporting.

Each engagement is described in full in our references.

Mass document production also raises the question of the accessibility of the documents it issues: this is where our document-production experience carries over directly, see our Accessibility practice.

Talk about your document platform