Contact centre migration: sorting the CapEx from the OpEx on the balance sheet

Ripping out a company call centre and putting it in the cloud isn’t just an IT project. It’s an accounting overhaul. For finance directors, it turns fixed capital on the balance sheet into recurring running costs on the P&L, shifting how working capital moves through the business month after month. If you only look at the monthly seat fee and ignore the broader commercial picture, your forecast EBITDA margins won’t stand a chance.

The old way: heavy upfront invoices and hardware lock-in

Under the legacy model, setting up shop meant cutting massive cheques before the first agent even picked up a handset. You had to buy physical PBX racks, dedicated comms servers, and proprietary switching gear. That went straight onto the books under plant and equipment, locked into three- to five-year depreciation cycles that left companies stuck using clunky, obsolete kit long past its prime.

On top of the initial hardware hit and perpetual software licences, on-premise set-ups brought a steady bleed of ancillary costs. You had mandatory maintenance retainers, third-party hardware insurance, and in-house telecom specialists handling board repairs and routine patches. When market demand dipped, those costs stayed exactly where they were: high and immovable.

How hosted subscriptions change the numbers

Moving to contact center as a service (CCaaS) completely reclassifies how money leaves the firm. Major capital outlays disappear, replaced by monthly operating charges that scale up or down depending on how many active licences your team actually uses.

Corporation tax treatment changes too. OpEx can usually be deducted against trading profits in the year the cost hits, keeping cash-flow forecasts clear and putting an end to lingering depreciation write-downs. That unfreezes working capital previously trapped in depreciating metal, handing the board dry powder to invest in projects with immediate commercial upside.

The rollout expenses vendors rarely mention

Any business case that doesn’t budget for implementation friction is going to miss the mark.

Porting over legacy 01, 02, and 0800 numbers always racks up administrative carrier fees, and integrating cloud telephony with in-house billing databases or dated CRMs usually demands bespoke middleware. Then there is dual running. Keeping the old on-premise PBX switched on alongside the new cloud environment is standard risk management to protect customer service, but it means paying two bills for a few weeks or months. Add in staff training – paying frontline staff their normal wages while they spend hours off the phones learning a totally new interface – and the initial cash requirement climbs quickly.

Building out a 36-month TCO and grilling the supplier

To see if the numbers actually work, you need to model total cost of ownership across at least three full years. That is roughly how long it takes for the initial CapEx savings to cross paths with cumulative subscription bills. Factor in metered call tariffs, long-term storage fees for compliance recordings, and the small overhead win of turning off power-hungry server racks in the comms room.

Before putting a signature on the contract, finance needs to drill into the small print. Look closely at how the vendor handles annual inflation uplifts, early exit penalties if headcounts fall, and what real clawback you get via service credits if their SLA collapses. Without ironclad contractual terms, operational flexibility can rapidly turn into creeping overheads.

Contributed content: this article was written by a third-party contributor and does not necessarily reflect the views of ABC Money. Editorial and Advertising Policy