%402x.svg){kind=icon}
Ask a production accountant what worries them most about moving off Sage 50, and it's rarely the new interface, the training, or even the cost. It's the data. Three, five, sometimes ten years of costs, cost centre splits, supplier histories and open balances, all sitting in a system they know inside out, about to be handed over to something new. That fear is completely understandable, and it's usually the single biggest thing standing between a production finance team and a decision to move to Microsoft Dynamics 365 Business Central.
The good news is that it doesn't need to be a leap of faith. This post walks through what actually happens during a Sage-to-Business Central migration, why generic migration approaches fall short for production accounting specifically, and how Just-Migrate, the data migration service built into Creative Total Media's implementation process, is designed around the way TV and film finance actually works.
Sage 50 Accounts has been a mainstay of UK small business finance for decades, and for good reason. It's familiar, relatively low-cost, and does a solid job of double-entry bookkeeping, VAT and basic reporting. Plenty of production companies started life on it, often because it was what their accountant recommended, or because the business began as a single small-scale operation with straightforward needs.
The trouble is that production finance isn't small-scale or straightforward for long. Once a company is running multiple productions at once, each with its own budget, cost centres, funders and Audio-Visual Expenditure Credit claim, Sage 50 starts to strain. Each production tends to live as its own separate company file, with no native way to consolidate or report across them in real time. There's no built-in job or production costing structure, so tracking spend against a production budget, by department, episode, or cost category, usually means bolting on spreadsheets alongside the core ledger. And as the number of active productions grows, reporting bottlenecks follow: finance directors end up manually stitching together numbers from several disconnected files just to get a single view of the business.
None of this is a criticism of Sage 50 doing what it was built to do. It's simply that production accounting, with its multi-production structures, cost centres, and specific reporting obligations under schemes like AVEC, asks more of a finance system than a single-entity accounting package was ever designed to deliver.
"Don't worry, your data will be fine" isn't a reassuring answer on its own. What finance teams actually want to know is what, specifically, is being preserved and how. In practice, a proper migration needs to account for:
Generic migration tools tend to treat all of this as one undifferentiated block of "data" to be transferred and mapped as best as possible. That approach can work reasonably well for a simple business with one entity and a flat chart of accounts. It's a much riskier proposition for a production company where costing structures and multi-production data are the whole point of the exercise, and where getting a cost centre mapping wrong doesn't just look untidy, it undermines the reporting a producer relies on to manage a live budget.
Industry-wide, poor data quality and mismatched structures are consistently identified as the most common causes of ERP migration problems, from duplicated records to lost historical context between the old and new systems, as Panorama Consulting's analysis of ERP data migration challenges sets out. The risk isn't really about the destination system. It's about what happens in between.
This is where Just-Migrate earns its place in the conversation rather than being an afterthought on a services page. It was built by Creative, a team that were Sage partners themselves before specialising in Business Central implementations for TV and film. That background matters, because it means the people building the migration tooling had already spent years inside Sage data structures, understanding exactly how production companies actually configure their nominal codes, departments and job references in practice, not just in theory.
Rather than a one-size-fits-all data dump, Just-Migrate is built to understand production accounting data specifically: how job costing structures need to translate into Business Central's dimension and project framework, how multi-production data should be separated and reconciled, and how cost centres need to map cleanly so that historical reporting still holds together after go-live. The result is a migration that preserves the integrity and accuracy of the data throughout, rather than a best-effort translation that finance teams then have to spend months reconciling by hand.
It's also worth being honest about what a migration tool can and can't fix. Just-Migrate isn't a substitute for a data cleanse, and Creative is upfront that switching systems is often the right moment to tidy up a chart of accounts that's accumulated a decade of quirks. But the point of a purpose-built tool is that the production-specific structures, the parts that generic accounting migrations routinely get wrong, are handled by people who understand what a job costing structure needs to look like on the other side.
It's worth being clear that data migration isn't a standalone event bolted onto the side of an implementation. It's one stage in a structured process, and that structure is itself part of what reduces risk. Creative's implementation journey runs through discovery, deployment, data migration, customisation, training, User Acceptance Testing (UAT) and go-live, with support continuing well beyond that point.
Discovery comes first for a reason: understanding a production company's operations, income types and cost structures properly is what makes an accurate data migration possible in the first place. Migration itself then happens alongside deployment, so the new system and the transferred data are tested together rather than in isolation. Crucially, migrated data doesn't go live untested. It passes through UAT, where the finance team itself checks that historical costs, balances and reports look right before anything is relied upon for day-to-day decisions. Go-live is supported directly by the team who built the migration, not handed off to a different department, and support continues afterwards. Framed this way, data migration is a well-supported step within a proven process, not a single point of failure sitting on its own.
Consider a production company partway through an active shoot, three years into using Sage 50 across several completed and in-flight titles. They can't afford a gap in cost reporting; producers need live visibility of spend against budget every week, and a funder is expecting AVEC-related reporting on schedule. Historical data from two wrapped productions needs to migrate cleanly for reconciliation purposes, while the current production's job costs need to carry forward without so much as a day's disruption to live reporting.
This is precisely the scenario Just-Migrate is designed around. Historical cost centre data from the completed productions is mapped and migrated with its structure intact, so past reporting remains accurate and auditable. The active production's open balances and current costs are migrated with a defined cut-over point, agreed with the finance team in advance, so there's no window where numbers are incomplete or duplicated. Testing happens in UAT before anything goes live, meaning the production accountant checks the migrated costs against their own records before trusting the new system for weekly reporting. The result is a switch that a producer chasing weekly cost reports never has to notice happened.
Data loss is the fear that keeps production finance teams on Sage 50 long after it's stopped serving them well. Once you understand what a proper migration actually involves, and that it's handled by a team who built their tooling specifically around production accounting rather than adapting a generic package, that fear tends to lose its grip.
If your production company is weighing up a move away from Sage 50, talk to Creative Total Media about how Just-Migrate fits into a supported implementation, from discovery through to go-live and beyond.
.avif){kind=logo}
.avif)
