Migrating from Sage to Cin7 Core: What Changes and What Stays the Same.

Migrating from Sage to Cin7 Core changes how inventory and financial data are managed rather than simply replacing one system with another. The key decisions are where the general ledger will live, how accounts will be mapped, and when the conversion date will take effect.

Key takeaways:

• Cin7 Core is primarily an inventory and order management platform, not a direct like-for-like replacement for Sage
• Businesses must choose between moving the ledger to Xero or QuickBooks Online, using Cin7 Core standalone, or maintaining a custom Sage connection
• Stock becomes a continuous operational record, with every receipt, pick, transfer, adjustment, and assembly updating quantities in real time
• Purchase receipts and purchase invoices are authorised separately, affecting stock quantities and accounting entries at different stages
• Costing methods are set per product and may change how inventory value and margins are reported
• Successful cutover depends on accurate account mapping, clean product data, balanced opening figures, and importing stock on hand only once

Sage has been the default finance system for UK product businesses for decades, and for good reason. It handles the ledger, it satisfies the accountant, and most finance teams know it well enough to work around its limitations. The trouble usually starts somewhere else entirely. Stock levels drift out of line with reality, someone is maintaining a spreadsheet to work out what is actually available to sell, and every new sales channel adds another manual reconciliation job.

At that point the conversation turns to Cin7 Core, and it almost always begins with the wrong question. People ask whether Cin7 Core is better than Sage. The more useful question is which parts of your current setup Cin7 Core is designed to take over, and which parts it deliberately leaves alone.

This guide sets out what genuinely changes when you move from Sage, what carries over untouched, and how the cutover works in practice. It is written for finance and operations leads who need to understand the shape of the project before committing to it.

Start here: Cin7 Core is not a like for like Sage replacement

This is the single most important thing to get straight, because a lot of failed projects trace back to a misunderstanding on this point.

Cin7 Core is an inventory and order management system that carries a financial module. It can operate as a standalone inventory and accounting system, or it can integrate with Xero or QuickBooks Online. Those two are the native accounting integrations. There is no native Sage connector, which means a Sage to Cin7 Core migration is really a decision about where your general ledger is going to live afterwards.

In practice there are three realistic routes.

Move your ledger to Xero or QuickBooks Online. This is the most common path for SMEs, because it gives you a supported, maintained integration with automated syncing of sales, purchases, and inventory movements. It does mean a second migration running alongside the first, so it needs to be planned as one project rather than two.

Run Cin7 Core standalone. The financial module includes a chart of accounts, bank accounts, bank reconciliation, manual journals, fixed assets, expense claims, and money in and out operations. For businesses whose accounting needs are relatively contained, this consolidates everything into one system.

Keep Sage and build a bridge. Technically possible through middleware or a custom integration against the Cin7 Core API, but you are then owning and maintaining that connection yourself. It can be the right answer where Sage is embedded in group reporting or a wider ERP estate, and the wrong answer if it is chosen simply to avoid a decision.

Which route suits you depends on your group structure, your accountant’s preferences, and how much of your finance process sits outside inventory. That assessment belongs in the discovery and design phase, before anyone touches a data file. If you are not yet certain the timing is right at all, it is worth reading our view on whether it is too early to make the move.

What changes

Stock becomes the system of record, not a month end figure

In most Sage setups, inventory is a balance that gets corrected periodically. In Cin7 Core, stock is transactional and continuous. Every receipt, pick, transfer, adjustment, and assembly moves quantities in real time, and the accounting consequences follow automatically in the background.

The practical effect is that inventory accuracy stops being a finance problem discovered at month end and becomes an operations discipline enforced daily. That is the main benefit of the move, and it is also the biggest cultural adjustment.

The timing of postings changes

This one catches experienced Sage users out, so it is worth stating plainly. In Cin7 Core, authorising the stock receipt on a purchase order updates physical quantities but does not itself generate accounting transactions. Authorising the purchase invoice generates the accounting entries but does not update quantities. The two events are separate, and both have to happen.

Once you understand it, the split is logical and it gives you much cleaner visibility of goods received but not yet invoiced. Before you understand it, it looks like the system has lost something. Brief your finance team on this specifically.

Your chart of accounts becomes a mapped structure

Cin7 Core provides a default chart of accounts, and you can import your existing one or build a custom version. What changes is control. If you integrate with Xero or QuickBooks Online, accounts are created and edited in the accounting system and appear in Cin7 Core in read only form, with every Cin7 Core account mapped to a corresponding account on the other side.

Getting this mapping wrong is the most common source of trouble after go live, because errors are quiet. Transactions still post, they simply post to the wrong place, and nobody notices until a management report looks strange. The Cin7 Core financial module documentation sets out which accounts are required and which are optional, and it is worth walking through with your accountant rather than accepting defaults.

Two details are easy to miss. Base currency must match between Cin7 Core and your accounting system. And a hierarchical chart of accounts is available in Cin7 Core standalone but not when accounts are integrated with Xero or QuickBooks Online.

Some financial functions move out of Cin7 Core

If you connect Xero, several parts of the Cin7 Core financial module become unavailable by design. Bank accounts, bank reconciliation, spend and receive money operations, expense claims, and manual journals are all handled in Xero instead. With QuickBooks Online the split is different again: bank account creation happens in QuickBooks, while reconciliation can be done in either system.

None of that is a limitation so much as a boundary. It does mean your finance team needs to know which screen to open for which task, and that is worth documenting before go live rather than discovering by trial and error.

You gain analysis you probably did not have

Cin7 Core supports accounting dimensions, which work like user defined tags applied to transactions so they can be grouped for analysis. Cost centre, customer group, product region, business unit, and similar categories can be defined to suit your reporting.

For businesses that have been forcing this kind of analysis through nominal code structures or department codes in Sage, this is usually the point where the reporting genuinely improves rather than just moving.

Costing becomes a per product decision

Cin7 Core sets costing at the individual product record, and it offers seven methods: plain FIFO, plus batch and serial numbered variants of FIFO, FEFO, and Special. All of them are actual cost methods. If your current stock valuation runs on an average or standard cost basis, that approach does not carry across, and the difference is worth modelling with your accountant before you commit, because it changes reported margin.

The method also drives the order in which stock is picked, so it is an operational decision as much as a financial one. Product setup therefore carries more weight than it used to. Cin7 Core does allow bulk costing method changes through a CSV export and import, but some changes are blocked outright, notably moving a SKU with existing transactions onto a serial numbered method. Decisions made during import tend to stick, which is one of several reasons to prepare your data first rather than importing what you happen to have.

What stays the same

It is easy to lose sight of how much does not change, so here is the other half of the picture.

Your statutory obligations. Nothing about the software you use alters what you owe or when. VAT returns, corporation tax, filing deadlines, and record retention periods are unaffected.

Your VAT process, in substance. Under Making Tax Digital rules, VAT registered businesses must keep specified records digitally and file returns using compatible software. Those records can sit across more than one system, provided the systems are digitally linked, and HMRC accepts API transfers and file imports as digital links while explicitly ruling out copy and paste. An API based sync between Cin7 Core and your accounting system fits comfortably within that. Confirm the specifics with your accountant, since the requirements depend on where your electronic account is maintained.

Your accountant’s year end. Trial balance, accruals, prepayments, depreciation, and statutory accounts continue exactly as before, produced from whichever ledger you end up running. Cin7 Core feeds that process rather than replacing it.

Payroll. Payroll sits outside the Cin7 Core financial module, so it stays wherever you run it today.

Your commercial data. Customers, suppliers, price lists, payment terms, and contact history all carry across. The records change format, not meaning.

Your chart of accounts logic. You are not obliged to redesign it. You can import your existing structure, and many businesses do, simplifying only where Sage forced complexity that no longer serves a purpose.

Your fixed asset register. Fixed assets, registration, and depreciation posting are available within Cin7 Core, so this capability carries over rather than disappearing.

The cutover: opening balances and the conversion date

The mechanics of the switchover are where migrations succeed or slip, and Cin7 Core is quite prescriptive about how it works.

You begin by setting a conversion date, which is the date you stop using your previous system and start using Cin7 Core. Opening balances are then entered as at the day before. Any transactions in Cin7 Core dated before the conversion date are disregarded, so the date is not a soft target.

Several points deserve attention before you start:

• The conversion date is effectively one way. Once opening balance data has been entered, the date cannot simply be changed. Correcting it means voiding opening balance tasks, sales, purchases, and manual journals, then re-entering everything.
• Balance Out By must read zero. Cin7 Core shows you the amount your balances are out by, and the number needs to be nil before you start trading in the system.
• Receivables and payables are entered invoice by invoice. Outstanding sales and outstanding purchases go in individually on their own tabs, and their totals must agree with the accounts receivable and accounts payable figures you entered on the opening balances tab.
• Bank balances follow the statement, not the ledger. Cin7 Core works from bank statement lines, so you enter the statement figure and post anything still in flight to an Unpresented Funds account, which clears once the item appears on the statement.
• Stock on hand imports once and only once. You import a product list, then a stock on hand template. Uploading the stock on hand file a second time creates new instances of products rather than updating quantities, so all subsequent corrections go through stock adjustment or stocktake instead.
• Customer credits do not import. Credit balances carried over from a previous accounting system cannot be brought across directly, and are handled as standalone credit notes in Cin7 Core.

The official guidance on the opening balance conversion process covers each of these in detail, including the account settings required for the Unpresented Funds account. Read it before you pick a date, not after.

One further sequencing rule matters more than it sounds: all of your settings, chart of accounts, account mapping, and tax rules need to be configured before any initial data load. Loading products, customers, suppliers, or stock into a partially configured system produces transactions coded against the wrong accounts, and unpicking that is considerably more work than setting it up properly first.

A realistic sequence for a Sage migration

1. Decide where the ledger will live. Xero, QuickBooks Online, standalone Cin7 Core, or a maintained bridge to Sage. Everything downstream depends on this.
2. Agree the conversion date with your accountant, ideally aligning it with a VAT period or financial year end to keep comparatives clean.
3. Build and map the chart of accounts, tax rules, and payment terms in full, before importing anything.
4. Clean the product data. Duplicate SKUs, inconsistent units of measure, and obsolete lines are cheaper to fix in a spreadsheet than in a live system.
5. Import products, customers, and suppliers, then load stock on hand once, and reconcile the value against the inventory account.
6. Enter opening balances, outstanding sales, outstanding purchases, and fixed assets until Balance Out By reads zero.
7. Connect sales channels and any warehouse or fulfilment integrations, and test order flow end to end. Our guide to syncing orders and finance covers what that connectivity should look like.
8. Run a parallel period if your volumes allow it, then cut over and keep Sage available in read only form for historical reference.

If you are also moving to Xero as part of this, our Xero inventory guidance covers how the two systems divide responsibility once they are connected.

What tends to go wrong

The failures are rarely technical. They are almost always sequencing or expectation problems.

Choosing a conversion date that suits the software timetable rather than the accounting calendar creates awkward comparatives for a year. Importing data before the chart of accounts is mapped generates postings that look fine and are not. Treating the Sage decision as something to settle later means the project stalls halfway. And assuming Cin7 Core will simply absorb everything Sage did leads to a go live where nobody knows who runs bank reconciliation.

Data quality deserves its own mention. Most of the common data integration challenges that surface during implementation were present in the source system long before the migration started. They just were not visible, because nothing depended on them being right. For a broader view of the whole process, our Cin7 Core migration guide sets out the full sequence, and if your current setup is part Sage and part spreadsheet, moving off manual systems is a useful companion read.

Final thoughts

A Sage to Cin7 Core migration is not a swap. It is a redrawing of the line between your inventory operation and your ledger, and the businesses that handle it well are the ones that decide where that line sits before they start moving data.

What changes is the operational half. Stock becomes continuous rather than periodic, postings split into separate events, your chart of accounts becomes a mapped structure, and several finance functions move to whichever accounting system you connect. What stays the same is everything your accountant and HMRC care about. Your obligations, your year end process, your commercial relationships, and the underlying logic of your accounts all survive the move intact.

The two decisions that carry the most weight are where your ledger ends up and when your conversion date falls. Get those right, configure fully before importing anything, and the rest of the project is largely disciplined execution.

If you are weighing up the options and want a straight answer on which route fits your business, speak to an expert and we will talk through your current Sage setup and what a sensible migration path looks like from here.

Frequently asked questions

1. Does Cin7 Core completely replace Sage?
   Not necessarily. Cin7 Core is primarily an inventory and order management system with its own financial module. It can run as a standalone inventory and accounting platform, or it can connect natively to Xero or QuickBooks Online. There is no native Sage integration, so the migration plan must define whether the ledger will move, remain in Sage through a maintained bridge, or be managed within Cin7 Core.
2. What is the biggest operational change when moving from Sage to Cin7 Core?
   Stock becomes a live transactional record rather than a balance corrected periodically. Receipts, picks, transfers, adjustments and assemblies update inventory continuously. This gives the business more accurate operational information, but it also means warehouse and purchasing processes need to be followed consistently every day.
3. Can the existing Sage chart of accounts be transferred to Cin7 Core?
   Yes. The existing structure can be imported or recreated, although some businesses use the migration as an opportunity to simplify accounts that are no longer useful. When Cin7 Core is connected to Xero or QuickBooks Online, the accounts are controlled in the accounting platform and mapped to their corresponding Cin7 Core accounts. The mapping should be reviewed carefully because incorrect postings may not become obvious until reports are examined.
4. How are opening balances transferred during the migration?
   A conversion date is selected, and opening balances are entered as at the previous day. Outstanding sales and purchase invoices are entered individually and must agree with the accounts receivable and accounts payable balances. Bank balances, fixed assets and stock on hand also need to be reconciled before trading begins, and Cin7 Core requires the Balance Out By figure to equal zero.
5. Can stock on hand be imported more than once?
   The initial stock on hand file should only be uploaded once. Uploading it again does not simply replace the previous quantities and may create additional product instances. Corrections after the first import should be handled through stock adjustments or a stocktake, which is why the opening stock file should be checked and reconciled before upload.
6. What should be decided before any data is imported?
   The business should first decide where the general ledger will live, agree the conversion date and configure the chart of accounts, account mappings, tax rules and payment terms. Product costing methods, units of measure and SKU structure should also be reviewed before import. Loading data into a partially configured system can create incorrect postings and make the migration considerably harder to correct.