A workable CCM migration roadmap runs backwards from the date your current platform leaves support or your contract ends. Twelve months is a comfortable horizon for a large estate. The exact plan differs per organisation: it depends on the systems you run today, the capabilities you need next, and the time you have. In outline it has four phases:
- Months 12 to 10: inventory and decide.
- Months 9 to 7: design the target and clean up.
- Months 6 to 3: convert and test in waves.
- Months 2 to 0: cut over and decommission.
The order matters more than the exact months. Overruns tend to come from two places: an incomplete inventory, and a platform provider without enough migration experience. That makes the first phase the one that deserves the most care, and professional help with the inventory of your current communications is where outside help pays back most.
Why plan back from the support date?
The support end date, or the contract end date, is the one fixed point in the project. Budgets, vendor choices and team availability all move. The date does not.
Planning forward from “when we have the budget” produces a plan that ends after the date. Planning back from the date shows immediately whether there is enough time, and if there is not, which phase needs more people or a smaller scope.
If the date is not known yet, that is the first task. Ask the vendor for it in writing, for the exact version you run.
Months 12 to 10: what goes into the inventory?
The inventory is a list of everything the old platform does, with an owner for each item. It covers:
- Templates and document types, marking which ones are still produced
- Channels and output: print, email, portal, SMS, archive
- Integrations: source systems, the print and mail provider, the archive
- Business rules hidden in template logic, such as which clause goes to which customer group
- Regulatory requirements per document family: mandatory wording, retention periods
- The business owner who signs off each document family
The phase ends with a decision: upgrade within the current vendor’s line, migrate to another platform, or move to a managed service.
Months 9 to 7: how do you design the target?
This phase decides how much work the next one contains.
- Retire before you convert. A template nobody has produced in a year does not move.
- Merge variants. Ten versions of the same letter with different footers become one template with shared content blocks. Consolidation can be complex work, and it is also where the largest efficiency gains of the migration sit. Experienced help makes it faster and safer.
- Set the operating model. Decide who owns content, who changes templates, who approves and who runs the platform. Writing this down now prevents the old arrangement from being rebuilt by default. For many organisations the right decision here is to hand template management to a specialist. The business keeps deciding what the communications say; the provider makes sure templates are maintained, keep working, and do not multiply into duplicates again.
- Plan the waves. Group the work by document family. Start with a family that is simple enough to learn on, then move to the regulated, high-volume families.
Months 6 to 3: how do you convert and test without risk to customers?
Convert one document family at a time. For each family:
- Run the old and the new platform side by side on the same real data.
- Compare every document in the run, rather than a sample.
- Have the business owner from the inventory sign off before the family goes live.
- Freeze changes on the old platform for that family while it is in migration, so you are not testing against a moving target.
The comparison results and sign-offs double as audit evidence later. Keep them.
Months 2 to 0: what has to be in place at cutover?
- Cutover per family, not one weekend for everything. A problem then stays contained to one family.
- Archive access. Documents produced on the old platform have to stay retrievable for their full retention period.
- A decommission date for the old platform, its servers and its licences, so the two do not run in parallel indefinitely.
The roadmap on one page
| Phase | Months before the date | Main output | Owned by |
|---|---|---|---|
| Inventory and decide | 12 to 10 | Complete inventory, route chosen | Business owner of customer communication, with IT |
| Design and clean up | 9 to 7 | Reduced template set, operating model, wave plan | Business owner, with the platform team or provider |
| Convert and test | 6 to 3 | Families converted, output compared, signed off | Platform team or provider, sign-off by family owners |
| Cut over and decommission | 2 to 0 | All families live, archive reachable, old platform switched off | IT, with the business owner |
What if you have less than twelve months?
Twelve months is a safe horizon. With a focused effort and experienced help, a migration can move considerably faster. Three things help:
- Shrink the scope. Move the regulated and high-volume families first. Retire low-volume documents or keep them briefly on the old platform.
- Ask about extended support. Some vendors offer it for a defined period. Get the terms and the end date in writing.
- Add capacity from outside. A managed service provider brings the platform team and the conversion work, so your own people can concentrate on the inventory and the sign-offs. Eclipse is one example of that model.
Frequently asked questions
What is a CCM migration roadmap?
A plan for moving templates, business rules, channels and integrations from a legacy customer communications platform to its successor. A good one works back from the support or contract end date and assigns an owner to every phase.
How long does a CCM migration take?
With a focused effort, a small, well-documented estate can move in a month or two. A mid-market estate usually takes several months, with discovery and testing taking most of the time.
Who should own the migration?
The business owner of customer communication, working with IT. The business rules and the approvals sit with the business, so a migration run by IT alone tends to discover them late.
Should we migrate everything at once?
No. Migrating in waves by document family limits the risk to one family at a time and lets the team learn on the simpler ones first.
What is the biggest risk?
Business rules nobody documented, which surface during testing instead of during the inventory.
When should you contact potential new suppliers?
As early as possible, ideally before the inventory starts. An experienced provider has been through every step of a migration, including the inventory and the discovery of business rules hidden in template logic, and can make both faster and more complete.
Related: CCM, CRM and marketing automation: who does what?
If your support date is closer than twelve months, this is a plan we help put together most weeks. Happy to work through yours.
