From on-premise to CCM as a service: what changes for your team


Thursday, Nov 12th 2026
The post title next to a grid of circles and quarter circles in Eclipse colours

CCM as a service means a provider runs your customer communication platform for you: the software, the hosting, the upgrades, the security and the daily production runs. Your organisation keeps the content and the decisions: what customers receive, which rules choose who gets which variant, and who approves a change. For the team, the work of keeping a platform alive goes away and more time goes to the communication itself. Business owners make routine content changes themselves in low-code tools, and IT is no longer the queue every edit waits in. Accountability stays with you.

What is CCM as a service?

A customer communications management (CCM) platform produces the letters, statements, emails, SMS and portal messages an organisation sends to its customers. On-premise, you license the software and run it yourself. With CCM as a service (CCMaaS), a provider hosts the platform, keeps it current and runs production under agreed service levels.

🟦 your organisation · 🟧 the provider

Activity Platform you run yourself CCM as a service
Deciding what the customer receives, approving changes 🟦 Business owner 🟦 Business owner
Routine content changes 🟦 Business owner, or IT if the tools are too technical 🟦 Business owner, in low-code tools
Building templates and business rules 🟦 IT 🟧 Provider, on the instruction of the business
Data feeds from source systems 🟦 IT 🟦 IT, with help from 🟧 the provider
Hosting, upgrades and security 🟦 IT 🟧 Provider
Monitoring production runs 🟦 IT 🟧 Provider and 🟦 IT, with the provider able to fix a run remotely
Compliance with sector rules 🟦 Your organisation 🟦 Your organisation

Why do organisations move to CCM as a service?

Usually to put more of their attention on the communication itself, and less on the platform underneath it. Three things change in practice:

  1. Less effort per change. A wording change or a new variant no longer waits for a release window, a server or the one specialist who knows the platform.
  2. A cleaner template estate. Over the years most on-premise platforms collect template sprawl: near copies of the same letter, variants for products that no longer exist, business rules that overrule each other. The move is a natural moment to clear that out, and a provider that has done it before helps decide what to merge, rewrite or retire.
  3. More time for content. Business owners and IT spend their hours on what customers read and on the data behind it, instead of on keeping software running.

Key takeaway: A managed service takes the platform work off your team so the attention goes to what customers read. Clearing out years of overlapping templates and rules is often the biggest gain of the move.

What moves off your team’s plate?

The work that keeps the platform running, which is also the work that is hardest to staff:

  • Patching and upgrading. On-premise, a major version upgrade is a project with its own budget and test cycle. As a service, it is part of what you pay for.
  • Servers, capacity for peak runs such as the annual statement, backups and disaster recovery.
  • Security of the platform and the certification evidence that goes with it.
  • Watching production at night and at month end, and restarting a failed run.
  • Support from a distance. Because the platform runs as a cloud service, the provider can get onto it remotely, pick up a problem straight away and roll out updates without an install round on your own servers.

What stays with your organisation?

Everything that decides what a customer reads, and the responsibility for it:

  1. The content. Wording, mandatory text, design, and the rules for which customer gets which variant.
  2. The approval. Every change is signed off by the named business owner of that document family.
  3. The data. Customer data comes from your source systems. Under the GDPR the provider is a processor that processes personal data only on behalf of the controller.
  4. Compliance. Accountability to your supervisor does not transfer with the work. The provider can produce the documents and the audit trail a regulator expects; answering for them stays with you.

That is the usual split. How independent you want to be, and where you want help, is up to you. Some organisations do all content work themselves from the first day. Others ask the provider to help with work that normally stays in-house, such as preparing template changes for the business owner to approve.

How do roles change in a managed CCM service?

Three roles shift. None of them disappears, and it helps to settle who owns, approves and runs what before the move.

  • Business owners do more themselves. Modern CCM platforms give them low-code editors to change wording or adjust a template within agreed rules, with the approval route as the safety net. Passing every edit through IT is the old way of working.
  • IT moves from running the platform to connecting it. Its work becomes the data feeds from source systems and the security requirements, and it no longer sits between the business and every content change. A CCM as a service provider usually helps build and maintain those connections, but IT stays involved: it knows the source systems and controls access to them.
  • Someone owns the service. A named service owner, often in IT, holds the contract, reads the service reports and is the provider’s counterpart. For many mid-market teams this role is new, and easy to forget.

When does on-premise CCM still make sense?

The classic trade-off is investing up front or paying over time. On-premise, you buy licences and servers and staff the platform yourself. As a service, you pay a fee that usually moves with volume. The market is moving towards subscription and volume-based models, but some organisations still choose to run CCM themselves. That tends to fit in two situations:

  1. Very large scale. Running a platform well brings real technical overhead and investment in servers. That only pays back at very high volumes, and once you include what the migration itself costs.
  2. Deep customisation. An installation of your own can be adapted further than a shared platform. That advantage is smaller than it used to be: with today’s APIs, a standard platform connects to almost any system.

How a managed service like CCMaaS can help

The question usually comes up at a fixed moment: an end-of-support date, a major upgrade with no budget behind it, or the platform specialist handing in notice. Compare the routes then on the team each one needs, how quickly business owners can change content, and how you would leave. Eclipse is one example of a provider that delivers CCM this way. Whichever provider you look at, ask before the demo how they would help clear out your current templates and rules, and how much of the work you can keep in-house if you want to.

Frequently asked questions

Does a CCM as a service provider decide what goes in my letters?
No. The provider builds and runs what the business asks for. The wording, the rules and the approval of every change stay with your business owners.

Do I have to send every content change to the provider?
No. Routine changes such as wording or a new variant of a letter are made by your business owners in low-code tools. The provider takes the technical work, such as a new channel, and helps IT with new data feeds. If you want help with content work as well, you can ask for it.

Who is responsible for compliance when CCM runs as a service?
Your organisation. A provider can produce the documents and the audit records. The obligation to comply, and to give your supervisor access, stays with you.

What happens to our templates and data if we change provider?
That is set in the contract: termination rights, a transition period and export of templates, content and archive in a usable format. The processor agreement states how personal data is returned or deleted.


Related: CCM, CRM and marketing automation: who does what?

If your on-premise platform is heading for its next big upgrade, we are happy to walk through what would move and what would stay.

How to choose a CCM platform: a 10-question checklist


Tuesday, Nov 10th 2026
The post title in large type next to the number 10 in orange

Choosing a CCM platform comes down to ten questions, asked in writing of every vendor on the shortlist and answered with a demonstration on your own documents. Features matter less than they seem, because most enterprise platforms can produce a good letter. What separates them is how they behave after go-live:

  1. Who can change content, and how quickly?
  2. Will you run the platform yourself, or buy it as a managed service?
  3. Which channels does one template reach?
  4. How does data flow from your source systems to the output channels, including print?
  5. Can it handle your peak runs?
  6. Can it prove what each customer received and who approved it?
  7. Where is the data processed, and what security evidence is there?
  8. How is the price built up?
  9. How do your existing templates get onto it?
  10. How do you leave again?

Each question below comes with what a good answer looks like.

Who can change content, and how quickly?

Ask the vendor to show a real change: a clause in a policy letter that legal wants reworded. Watch who makes it and how many steps it takes.

The old way is that every edit goes through IT, joins a release, and reaches customers weeks later. Modern low-code tools let business owners make content changes themselves, inside guardrails that IT sets once: approved content blocks, locked mandatory text, and an approval step before anything goes live.

A good answer: a business owner makes the change in a browser, a second person approves it, and it is in production the same day or the next. If AI helps draft the text, the same approval applies. AI can help draft; a person approves.

Should you run the platform yourself or buy a managed service?

This is the decision that shapes the rest of the checklist, because it decides what your own IT has to staff.

Activity Platform you run yourself Managed service
Hosting, upgrades and monitoring IT Provider
Integrations with source systems IT Provider, per your instructions
Content changes Business owners Business owners
Approval of what customers receive You You
Incident handling IT Both, with the provider able to fix remotely

Running it yourself gives full control and needs IT capacity for a system that is not your core product. A managed service moves the technical work to the provider while the content, the approvals and the responsibility stay with you. Eclipse is one example of the managed route, under the name CCMaaS. That stands for CCM as a service: the provider runs the platform, and you keep the content and the approvals. Who owns, approves and runs what is worked out in more detail in our post on the customer communication operating model.

A good answer from any vendor: a clear list of what they do, what you do, and what that costs, for the model you are buying.

Which channels does one template reach?

Customers receive the same message on paper, by email, by SMS, in a portal and through WhatsApp. In the Netherlands, government bodies also send digital post through the MijnOverheid Berichtenbox, which only organisations connected to MijnOverheid can use.

A good answer: one template and one set of business rules produce every channel, so a wording change is made once. Ask which channels are live for other customers today and which are on a roadmap.

How does data flow from your source systems to the output channels?

Customer data sits in several systems: policy administration, core banking, billing, CRM or case management. One letter often needs data from more than one of them, and every output channel, print included, expects its own format. Questions to ask:

  • Does the platform bring data from different source systems together in one canonical data model, so every template works from the same set of data?
  • What happens when two sources conflict, or a field is missing? Does the run stop, and who is notified?
  • How does it merge records from several sources, and how can you check that the merge was right?
  • How does data move through the platform, and is it encrypted in transit and at rest?
  • How are the output channels connected, including your print partner, and who sees whether each hand-over succeeded?

A good answer: one data model for all templates, written rules for conflicts and gaps with an alert to a named person before anything goes out, encryption along the whole route, and tested connections to every channel and the print partner, with a report of each hand-over.

Key takeaway: A letter is only as correct as the data behind it. Ask to see what the platform does with conflicting or missing data before anything reaches a customer.

Can it handle your peak runs?

Annual statements, indexation letters and tax documents arrive in peaks, which is where scalable CCM earns its keep. Ask the vendor to describe a run at your own peak volume, what happens if it fails halfway, and how capacity grows. Does the platform scale up and down automatically, or does someone have to request extra servers or storage and wait for them?

A good answer: capacity follows the load without a request or a wait and drops back afterwards. The run restarts from the point of failure without duplicates, and you are told what was produced and what was not.

Can it prove what each customer received and who approved it?

Supervisors and auditors ask for one customer’s communication on one date: what was sent, which template version produced it, who approved that version, and whether it was delivered. Our post on the customer communication audit trail sets out what regulators expect here.

A good answer: the platform records all four at production time, for every channel, and you retrieve them for one customer in minutes. A PDF archive alone covers only the first.

Where is the data processed, and what security evidence is there?

Ask for the region where customer data is processed and stored, who at the provider can access it, and which subprocessors are involved. EU rules allow transfers outside the EEA only with special safeguards so that the protection travels with the data. DORA does not impose data localisation, but it does expect a financial entity to know where its outsourced functions are provided and where data is processed.

A good answer: an EU region named in the contract, a current ISO 27001 certificate whose scope covers the service you are buying, and an assurance report such as ISAE 3402 or a SOC 2 Type II report if your auditor asks for one.

How is the price built up?

CCM prices usually have three parts: a licence or subscription, an implementation estimated as hours times a rate, and running costs that are fixed or move with volume. How those parts balance depends on the model:

  • On premise: an upfront investment in licences, infrastructure and implementation, then the cost of your own IT to run and upgrade it.
  • CCM as a service: a smaller upfront investment, mostly implementation, and an operational cost over the contract that covers hosting, upgrades and monitoring.

A good answer: a price you can project over the contract term at your own volumes, including peaks, with every trigger for a change written down. Ask whether the price follows what you actually use, or whether you pay for capacity sized for the peak that sits idle the rest of the year. Ask too what is included in running: upgrades, monitoring, archive and support hours.

How do your existing templates get onto it?

In most selections an existing platform is being replaced. Ask the vendor how they inventory your current templates, how they convert them, and how they prove the new output matches the old. The template count is also where migration estimates most often go wrong.

A good answer: an inventory first, unused templates retired before conversion, and every document family tested side by side on real data before it goes live. Experienced help on the inventory is what makes a faster timeline possible.

How do you leave again?

The best time to agree an exit is before signing. Ask in what format your templates, business rules, content blocks, archive and audit records leave the platform, and how long the provider supports a transition.

Ask too whether your templates could move to another platform at all. Templates built on a widely used composition engine may be easier to move than a proprietary format, so ask which export format they use and whether another platform can read it.

Regulation now backs this up. The EU Data Act has applied since 12 September 2025, requires providers of cloud and software services to remove obstacles to switching, and removes switching charges entirely from 12 January 2027. For financial entities, DORA requires exit strategies for ICT services that support critical or important functions, with a transition period in the contract.

A good answer: export formats named in the contract, a transition period with the provider’s support, and archive access for the full retention period after the contract ends.

Key takeaway: Templates, rules and archive should be able to leave in a format another platform can use. Getting that in writing costs little before signing and a lot after.

How to use the checklist

  1. Send the ten questions in writing to every vendor on the shortlist.
  2. Ask each one to demonstrate the content change and the audit trail question on one of your own documents.
  3. Score the answers yourself, against what your organisation needs, before price enters the discussion.

The written answers then become part of the contract.

Frequently asked questions

Who should be involved in choosing a CCM platform?
The business owners of the main document families, IT, compliance and procurement. Business owners judge content changes and approvals, IT the data flow and integrations, compliance the audit trail. One person owns the final decision.

What should the demonstration on our own documents include?
One of your more complex existing documents, a content change made and approved by a business owner, and the retrieval of what one customer received on one date. Add a test file with a missing or conflicting field to see how the platform reports it.

How many vendors belong on the shortlist?
Few enough to run a demonstration on your own documents with each, in practice three or four. A longer list usually gets a lighter test and answers that are harder to compare.

What is the difference between a CCM platform and a CRM or marketing tool?
A CCM platform produces regulated, personalised documents and messages across channels from governed templates. CRM manages the customer relationship, and marketing automation runs campaigns. See CCM, CRM and marketing automation: who does what?


Related: The evolution of CCM to CXM: from documents to experiences

If you are building a shortlist and want a second view on the answers you get back, we are happy to go through them with you.

A CCM migration roadmap: planning a legacy platform’s end of life in 12 months


Friday, Nov 6th 2026
The post title next to a migration plan with milestones, in Eclipse colours

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:

  1. Months 12 to 10: inventory and decide.
  2. Months 9 to 7: design the target and clean up.
  3. Months 6 to 3: convert and test in waves.
  4. 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.

  1. Retire before you convert. A template nobody has produced in a year does not move.
  2. 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.
  3. 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.
  4. 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:

  1. Shrink the scope. Move the regulated and high-volume families first. Retire low-volume documents or keep them briefly on the old platform.
  2. Ask about extended support. Some vendors offer it for a defined period. Get the terms and the end date in writing.
  3. 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.

What a CCM migration actually costs, and where estimates go wrong


Monday, Nov 2nd 2026
The post title next to a cost estimate with the total highlighted, in Eclipse colours

A CCM migration has three cost components, one for each stage of the project:

  1. Investigation: finding out what the old platform actually does, and choosing the route.
  2. Implementation: rebuilding templates, business rules, channels and integrations on the new platform, and testing them.
  3. Running: the platform after go-live, including the licence or service fee.

The estimate that reaches the board usually holds a licence and a conversion quote. Investigation is often missing, and running costs are left to a later budget. Those two lines decide whether the project lands on budget.

What are the cost components of a CCM migration?

Component What is done How it is usually priced
Investigation Inventory of templates, business rules, channels, integrations and owners; choice of route Estimated hours times an hourly rate, often as a separate first phase
Implementation Templates and logic rebuilt on the new platform, output tested, sign-off per document family Estimated hours times an hourly rate
Running Platform, hosting, upgrades, support and archive after go-live A licence plus your own team, or a primarily volume-based fee

What happens in the investigation stage?

The investigation writes down what the old platform does: every template still in use, every channel, every integration with a source system or a print provider, every business rule buried in template logic, and the business owner who signs off each document family.

Most organisations assume this list exists. What exists is usually a folder of templates and a few people who remember why a particular clause goes to a particular customer group. Skipping the investigation does not save the work. It moves it into implementation, where it is more expensive and comes later.

The stage ends with a choice of route: upgrade with the current vendor, migrate to another platform, or move to a managed service. That choice sets the cost of the other two stages.

How is implementation priced?

Implementation is usually quoted as an estimate of hours times an hourly rate. The hours depend less on the number of templates than on the logic inside them: which variant is sent when, which clauses are mandatory for which product, which data field drives which paragraph. A letter with thirty conditional branches takes many times longer to rebuild than a letter with none, and both count as one template.

Two things keep the estimate honest:

  1. Retire before you convert. A template nobody has produced in a year does not move, and does not get paid for. This is where experience pays off: a CCM partner that has done this before knows which templates can go, which can be merged, and where the logic is hiding, and reaches that shortlist in less time than an internal team working from the folder.
  2. Agree what the estimate covers before you accept it. It should include the business rules and the comparison of old against new output on real data. Anything that is not in the estimate is added later, at the end of the project, when there is no room left to say no.

How are running costs priced?

Running costs usually follow one of three models:

  1. Licence model. A licence or subscription for the platform, plus your own team to run it, the infrastructure, the upgrades and the archive. Each of these is a separate line, and most of them sit outside the project budget.
  2. Buying the software. A one-off purchase of a perpetual licence, with a yearly maintenance fee on top and the same team, infrastructure and upgrades as the licence model. This used to be the norm and is now rare, as vendors have moved to subscriptions.
  3. Volume-based managed service. A primarily volume-based fee, set by the number of communications you send, covering the platform, hosting, upgrades and support. Eclipse prices its managed service this way, so the cost moves with what you actually produce.
Upgrade with the current vendor Migrate to another platform Managed service
Pricing basis Licence plus your own team Licence plus your own team A primarily volume-based fee
Platform team Retained Retained, retrained Not needed; the provider runs it
Upgrades and patching Yours Yours Usually included in the fee

Whichever model you choose, the old platform keeps costing money until it is switched off. Put its decommission date in the plan and in the budget.

How to build an estimate that holds

  1. Get the support end date or contract end date in writing.
  2. Fund the investigation as its own stage, before anyone quotes implementation.
  3. Retire unused templates and merge variants before counting what moves.
  4. Agree what the implementation estimate covers, including business rules and testing, before you accept it.
  5. Add the running cost of the first two years for each route, including the old platform until it is switched off.

Then compare the routes on the total of all three components, not on the licence.

Frequently asked questions

How much does a CCM migration cost?
There is no useful single figure. The total depends on the number of document families, the business rules inside them, the channels and integrations involved, and the running model you choose. A complete estimate covers investigation, implementation and running.

What is the biggest hidden cost in a CCM migration?
Business rules that nobody documented. They are invisible in a template count and surface late, when they are rebuilt under time pressure. A proper investigation is the cheapest way to find them.

Is a managed CCM service cheaper than running the platform yourself?
That depends on your volume and on the team you would otherwise keep. A primarily volume-based fee makes the cost easy to forecast and replaces a staffing problem with a contracted service.

How long does the old platform keep costing money?
Until it is decommissioned. Put a decommission date in the plan and in the budget.


Related: Understanding the cost and value of CCM solutions and CCM, CRM and marketing automation: who does what?.

If you are putting a migration estimate in front of a board this quarter, this is the breakdown we walk through most weeks. Happy to go through yours.