ERP implementation: phases, data migration and cost

What an ERP implementation involves

ERP implementation is the project that takes a business from its current tools to one shared system: agreeing scope, configuring the software, moving the data, testing, training and switching over on a fixed cut-over date. Before you start you need three things: a named owner for every process, a clean opening trial balance at the cut-over date, and a decision on what history to leave behind.

Most of the work is not technical. The software is usually the smaller part of the budget; the larger part is the time your own people spend deciding how the business should run in the new system, cleaning data and learning new screens. A project that treats implementation as an IT install, rather than a change in how the business records sales, purchases and stock, is the project that overruns. This vendor-neutral plan suits a small or mid-sized UK company moving to a cloud ERP.

The six phases of an ERP implementation

Methodologies use different names, but almost every ERP implementation roadmap passes through the same six phases. Each phase ends with a sign-off, so nobody configures screens before the scope is agreed, and nobody migrates data before the configuration is stable.

A phased go-live, one site or one module at a time, lowers risk for groups with several companies or sites. A single-company business usually does better with one cut-over: running half the business in each system creates more reconciliation work than it saves.

• Plan and scope: business case, objectives you can measure (for example, close the month in 5 working days instead of 12), budget, team, cut-over date and what is out of scope.
• Design (fit-gap): walk through each process, from quote to cash, purchase to pay, stock and month-end, and record where the standard software fits and where you will change a process or accept a workaround.
• Configure: company settings, chart of accounts, tax rates, branches and warehouses, document numbering, users, roles and approval limits.
• Data migration: extract, clean, map and load master data, open items and opening balances, with a trial load before the real one.
• Test and train: run real documents end to end, reconcile the results, and train users on their own tasks rather than on every menu.
• Go-live and hypercare: switch over on the cut-over date, then give users daily support for the first two to four weeks and close the first month together.

Roles: who you need on the implementation team

An ERP implementation team for a small business can be four or five people working part-time on the project. What matters is that each role below has a name next to it and hours set aside in that person's week.

• Executive sponsor: the owner or managing director who settles scope disputes and protects the team's time.
• Project lead: runs the plan, the issue log and the weekly check-in; often the finance manager in a small company.
• Process owners: one person each for sales, purchasing, stock and finance who signs off the design and the test results for their area.
• Data owner: responsible for the quality of customer, supplier, product and balance data, and for signing off each load.
• Accountant or bookkeeper: confirms the chart of accounts, the VAT set-up and the opening trial balance.
• Vendor or implementation partner: configures, advises on standard ways of working and fixes defects. Agree in writing what they do and what your team does.
• Super-users: one or two people per area who learn the system first and become the first line of support after go-live.

ERP data migration: what to move and what to leave

Data migration is where ERP implementations most often slip, because data that looked fine in the old system turns out to contain duplicates, missing VAT numbers or products nobody has sold in years. Decide each group below deliberately.

Do not migrate years of posted transactions unless your auditor or a regulator needs them in the new system. It is cheaper and safer to keep the old system, or full exports from it, available read-only. HMRC generally expects VAT records to be kept for at least 6 years, so decide where that history will live before you switch the old system off.

• Master data: chart of accounts, customers, suppliers, products, units, price lists and warehouses. Clean before loading: merge duplicates, archive inactive records, complete VAT numbers and payment terms.
• Open items: unpaid sales invoices and unpaid supplier bills, so you can collect and pay after go-live, and open sales or purchase orders if you have them.
• Balances: an opening trial balance at the cut-over date, a stock count valued at cost, and bank balances agreed to statements.
• History: summary figures for comparison reports, such as monthly sales by account for last year, rather than every transaction.
• Mapping file: one spreadsheet showing each old account, tax code and product group against its new equivalent, signed off by the accountant.
• Trial load: load everything into a test company, run the trial balance and ageing reports, compare them with the old system, fix and reload.
• Final load: freeze the old system, extract the cut-over figures, load, reconcile and sign off before the first new transaction is entered.

Worked example: an opening trial balance at cut-over

A UK trading company switches system on 1 April 2027, the first day of its VAT quarter. After closing March in the old system it extracts the trial balance below as at 31 March 2027. The opening balances in the new system must reproduce it exactly.

Three checks then prove the migration: the customer ageing report must total 12,600, the supplier ageing report 9,800 and the stock valuation report 21,000. If any of them differs, find the difference before go-live. Afterwards it is mixed with new transactions and far harder to trace.

• Bank: debit GBP 18,400, agreed to the 31 March bank statement.
• Trade receivables: debit GBP 12,600, made up of 23 unpaid customer invoices loaded as open items.
• Inventory: debit GBP 21,000, from the stock count on 31 March valued at cost.
• Trade payables: credit GBP 9,800, made up of 14 unpaid supplier bills loaded as open items.
• VAT payable: credit GBP 3,200 for the January to March return, paid after cut-over.
• Bank loan: credit GBP 10,000.
• Share capital: credit GBP 1,000. Retained earnings: credit GBP 28,000.
• Totals: debits 18,400 + 12,600 + 21,000 = GBP 52,000; credits 9,800 + 3,200 + 10,000 + 1,000 + 28,000 = GBP 52,000.

Choosing the cut-over date and the go-live approach

Pick a cut-over date that starts a clean reporting period. The start of the financial year is ideal, because the opening balances are the closing balances your accountant has already reviewed and comparisons stay simple. The start of a VAT quarter is a good alternative, because one VAT return then comes entirely from one system.

That matters under Making Tax Digital for VAT. HMRC's VAT Notice 700/22 requires VAT-registered businesses to keep specified records digitally in functional compatible software, and data moving between programs must travel by digital link, not by retyping. If a quarter has to be split between two systems, agree with your accountant beforehand how the two sets of figures will be combined for the return.

Then decide how to switch. A big-bang cut-over moves everything on one date. A parallel run keeps both systems going for a month, which doubles data entry for little gain in a small business; a better compromise is to re-run one closed month in the test company and compare the results before go-live.

How long an ERP implementation takes

There is no standard duration, so treat any figure as a planning assumption rather than a benchmark. The timeline is driven by the number of companies and sites, the number of processes that change, the volume and quality of the data, the integrations you need and, above all, how many hours a week your own team can give the project.

As planning assumptions: a single company with one site, standard processes and clean data can plan for 4 to 8 weeks on a cloud ERP. Several sites, stock in more than one warehouse, or data that needs heavy cleaning points to 2 to 4 months. Multi-company groups with integrations, manufacturing or bespoke development should plan in quarters rather than weeks. An 8-week plan for a single-site company looks like this:

• Weeks 1 to 2: scope, team, cut-over date and fit-gap workshops.
• Weeks 2 to 3: configuration of company settings, tax rates, chart of accounts, locations and users.
• Weeks 3 to 5: data cleaning, mapping file, trial load and reconciliation.
• Weeks 5 to 6: end-to-end testing with real documents and user training.
• Week 7: data freeze, closing figures from the old system, final load and sign-off.
• Week 8 onwards: go-live, daily hypercare and the first month-end close in the new system.

What an ERP implementation costs: the drivers

ERP implementation cost has six parts, and the subscription is often the smallest of them. Count all six for the first year, then compare the total with the cost of carrying on as you are, including the hours spent re-keying data between systems and fixing the errors that re-keying causes.

• Software: subscription per user or per company, plus add-on modules, extra branches and any usage-based fees.
• Implementation services: a partner's or vendor's days for configuration, data loads and training, or a fixed-price package.
• Internal time: the hours your team spends in workshops, cleaning data, testing and training. It is a real cost even though no invoice arrives.
• Data work: cleaning, de-duplicating and mapping, which grows with the age of the old system.
• Integrations and customisation: links to an online shop, payroll, banks or EDI, and any bespoke development. Every customisation also adds cost at each upgrade.
• Contingency: 10 to 20 per cent of the people cost, because the issues you have not found yet are usually in the data.

Worked example: a first-year implementation budget

A single-site UK company with one finance user on the system does the implementation in-house and buys a little accountant time. All figures exclude VAT, and the day rates are assumptions chosen for illustration, not market data.

The lesson holds at any size: the budget is mostly people's time, so protecting that time is the most effective cost control you have.

• Software: Skyline Nexus ERP Solo, first 12 paid months with the launch offer, GBP 157.50.
• Internal time: 15 days at an assumed GBP 200 a day, GBP 3,000.
• Accountant review of the chart of accounts, VAT set-up and opening balances: 2 days at an assumed GBP 400 a day, GBP 800.
• Contingency: 15 per cent of the people cost of GBP 3,800, GBP 570.
• Total first-year budget: 157.50 + 3,000 + 800 + 570 = GBP 4,527.50.
• Share of the budget spent on software: 157.50 / 4,527.50 = about 3.5 per cent.

Testing, training and the go-live checklist

Test with real documents from last month, not invented ones. Each process owner enters a full cycle, such as a quote turned into an invoice and a credit note, a purchase received and paid, and a stock count adjustment, then checks that the ledger, the VAT report and the stock reports show what they expect.

Train people on the five or six tasks they do every day, in the test company and with their own data, as close to go-live as possible. Short task sheets work better than long manuals. Then work through this checklist before the first live transaction:

• Opening trial balance loaded and agreed to the old system's closing balance.
• Customer and supplier ageing totals agree to the receivables and payables control accounts.
• Stock valuation agrees to the inventory balance, and stock quantities agree to the count.
• Tax rates, invoice numbering and invoice layouts approved; a test invoice checked against the UK VAT invoice rules.
• Users created with the right roles and site access; test users removed.
• Automatic posting, fiscal periods and approval settings switched on and checked.
• Old system frozen, read-only access kept and history exports stored.
• Hypercare rota and an issue log agreed for the first four weeks.

Why ERP implementations fail, and how to avoid it

The usual causes are organisational far more often than technical, and each has a simple counter-measure if it is agreed at the start.

• Scope creep: every 'while we are at it' request moves the date. Keep a list for phase two.
• Customising to copy the old system: adapt the process to the standard software unless the difference is a real advantage for your customers.
• No time for the team: if key users keep their full day job, testing and data cleaning slip first.
• Dirty data: duplicates and wrong opening balances undermine trust in the new reports from day one.
• Training too early or too general: people forget what they learned two months before go-live.
• No owner after go-live: the system drifts unless someone owns settings, users and the month-end routine.
• No measurable objective: if success was never defined, nobody can say whether the project worked.

Implementing Skyline Nexus ERP

Skyline Nexus ERP is a cloud service, so there is no server to install; implementation is configuration and data. Master data comes in through import screens with spreadsheet templates: products, opening stock, customers and suppliers (with each contact's opening balance, payment terms and credit limit), the chart of accounts as CSV, XLSX or XLS, budgets, fixed assets and employees. Sales and purchases can also be imported with a preview, and an import batch can be reverted if your checks fail.

The general ledger opening balance is entered on the Opening Balances screen, which accepts the set only when total debits equal total credits; customer and supplier balances are entered per contact rather than on the receivables and payables control accounts. Before the first posting, create the fiscal year and its periods, because a posting dated outside an open period is refused, and switch on the Auto-post settings for sales, purchases, payments and expenses, which stay off until an administrator turns them on. Roles, permissions and location access control who sees what, and changes to accounting records are logged in the Audit Trail with the user and the old and new values.

Two points for UK businesses. VAT reports and a prefilled VAT return form give you the figures, which you submit through MTD bridging software or your accountant's MTD software while direct MTD filing is being rolled out; UK payroll stays in your payroll software for now, because local payroll is rolled out country by country. Skyline Nexus ERP Solo costs GBP 15 a month plus VAT for one user and one business location, and every plan starts with a free first month (30 days, all modules, your own data, no card needed). Under the launch offer, valid until 31 January 2027, the first 3 months cost GBP 7.50 each on monthly billing, or GBP 150 on annual billing covers 15 months. Start the free month, run your trial load in it, and use the checklist above before you go live.