Request a quote
Emergency SectorsCareers About us Blog Get in touch
Two colleagues at a whiteboard covered in technical diagrams in a glass-walled meeting room

ERP implementation: the IT side of the plan

In an ERP implementation the implementation partner configures the package and the business decides how its processes will run. Alongside sits a second list that no vendor’s ERP implementation plan covers in full: accounts, devices, printers, integrations, the data from the old system and the day everything switches over. This is that list.

7 min read Written by the ITproposal team
Short answer

An ERP implementation has two tracks: the package and the processes (partner and business), and everything the package runs on and talks to (IT). The second track often has no owner.

Data does not move in one go but in trial migrations, with reconciliation figures that someone in the business signs off before the cutover date is fixed.

For packages we carry, we configure the ERP ourselves as well. Process decisions stay with the business, and the tax and legal review belongs to the accountant or lawyer.

ERP implementation: two tracks, one plan

An ERP implementation is usually planned from the package outwards: configuration, customisation, testing, training, go-live. That track belongs to the implementation partner and to the people who know how purchasing, stock, invoicing and finance actually work. The second track is less visible and cuts straight across it: the environments the package runs in, the accounts people sign in with, the devices and printers, the integrations with other systems, and the data that has to come out of the old system.

Put that second track in the same ERP implementation plan, with its own owner. Projects rarely stall on a field configured the wrong way; they stall on a label printer that cannot handle the new format, a bank integration missing a certificate, or a user with no account on Monday morning.

Ask the partner at the start for the list of what they expect from IT, with dates. Whatever is not on it, someone will discover in test week.

Test, acceptance and production

In practice an ERP runs in at least two environments, often three: a test environment where the partner configures, an acceptance environment where the business tests with real data, and production. With a cloud ERP the vendor runs those environments; with a package on your own or hosted servers, they are your responsibility.

  • Cloud: sort out the network side. Bandwidth and latency to the service from every site and the warehouse, allowed addresses in the firewall, and what happens when the internet line drops.
  • Own or hosted servers: capacity to the vendor’s requirements, a backup you have actually restored before go-live, patching, and who gets the call at night.
  • Either way: the acceptance environment holds real data, so it gets the same access rules as production. A test system with a copy of the customer file and a shared password is a data breach waiting to happen.

Accounts, sign-in and roles

Have the ERP sign people in through the identity platform you already run (for many organisations Microsoft Entra ID), with single sign-on and multi-factor authentication, rather than a separate list of usernames and passwords. Joiners and leavers then work as they do everywhere else: whoever leaves loses access to finance in the same single step.

  • Roles on paper first. Who may approve purchase orders, who may prepare payments, who sees salaries. That is a business decision; the partner configures it, IT maps the groups.
  • Segregation of duties. The same person should not create a supplier and approve the payment to that supplier. Your auditor will ask.
  • Service accounts and keys. Integrations sign in with their own accounts or API keys. Those live in a vault, have an owner and do not quietly expire.

How to set that up across the whole estate is covered on our page about identity and access management.

Devices, printers and scanners

An ERP touches more devices than the finance team’s laptops. Before test week, build an inventory of everything that has to work with it, per site:

  • Workstations: supported browser or client, operating system version, and whether the client is deployed by software distribution rather than by hand.
  • Printers: invoices, delivery notes and above all labels. A warehouse label printer with the wrong format or an outdated driver stops dispatch.
  • Handheld scanners and terminals: which models the package supports, and whether the warehouse Wi-Fi reaches between the racks.
  • Home and field staff: remote access, on which devices, and under what conditions.

Roll out clients and drivers a week before cutover, not on the day. Then Monday starts with a workstation that works rather than an installation still running.

Integrations: what talks to what

An ERP rarely stands alone. Put every integration on one list: the bank, the webshop, e-invoicing, the carrier, EDI with customers or suppliers, payroll, reporting. For each, note which way the data flows, how often, and who builds it.

The builder is usually the implementation partner or the vendor of the other system. What IT arranges is everything around it: firewall rules, certificates and their expiry dates, service accounts, and an alert when an integration stops. An integration that fails overnight and is only noticed when a customer rings is not a technical problem but a missing owner.

In the UK, check how the package handles Making Tax Digital for VAT: built in, or through a bridging service. If it is the latter, that is another integration on your list.

The data: trial migrations and reconciliation

Data handover is where an ERP implementation most often overruns. The approach that works: not one migration but several trial migrations, each with the same scripts, until the result matches in two consecutive runs.

  • What moves. Master data (customers, suppliers, items) almost always; open items and stock on cutover day; history often not, it stays readable in the old system.
  • Clean before, not after. Duplicate customers and obsolete items are tidied up in the old system by the business. What moves across dirty stays dirty.
  • Count and sign off. Number of customers, the debtors balance, stock value per site: before and after, signed off by someone in the business. IT supplies the figures; the finance lead says whether they are right.

How to plan any migration without losing anything is in our article on data migration without loss.

Cutover and the weeks after

Cutover is a runbook, not a date. It covers the moment the old system goes read-only, the final migration of open items and stock, the reconciliation, and a go/no-go point with criteria agreed in advance. If the figures do not match you go back to the old system, and you have tested that fallback.

  • Pick the date with finance. Not in the middle of a month-end close, not in the busiest week of the year, and with a few quiet days after.
  • Prepare the service desk. The first weeks bring questions about the package and questions about the workstation. Agree who takes which, so nobody is passed on twice.
  • Keep the old system. Read-only, backed up, for as long as your record-keeping obligations run. Also record who cancels its licence, and when.

Where our work stops

What we do. Packages we carry, such as AFAS, Exact, SAP and Sage, we supply and configure; whether support stays with us afterwards is a separate choice. Alongside that we run the IT track from this article: the infrastructure, the workstations, printers and scanners, the links to network and identity, and the data handover. For a package we do not carry, we work with the vendor or its implementation partner: they configure the package, we do the rest of this list.

What stays with you, and with others. Process decisions belong to the business: which way of working, which chart of accounts, which approval steps and who may do what. We put options forward and configure what you decide; we do not decide it. Whether the configuration and the migrated figures are right for tax and legal purposes is for your accountant or lawyer to check, not us.

Frequently asked

Questions we get about this

The five that come up most often.

What are the phases of an ERP implementation?

Usually preparation, configuration, testing in an acceptance environment, training, cutover and a period of hypercare. Alongside those package phases runs an IT track: environments, accounts and roles, devices and printers, integrations and trial data migrations. Plan both in one schedule, or they collide in test week.

Why do ERP implementations overrun?

Often because of the data: dirty master data, a migration rehearsed only once, or reconciliation figures nobody signs off. Also because of loose ends without an owner, such as a label printer, an integration with an expired certificate or missing accounts. Trial migrations and a list of what IT must deliver prevent most of it.

What is an ERP cutover?

The planned switch from the old system to the new one. The old system goes read-only, the final open items and stock are migrated, the business checks the reconciliation, and a go/no-go decision is taken on criteria agreed in advance. If it does not match, you fall back to the old system along a path tested beforehand.

Should we keep the old ERP system after go-live?

Usually yes, as a readable archive. History often does not move across, and you still have to be able to produce those records for years under tax and company record-keeping rules. Set the old system to read-only, back it up and agree who cancels its licence and when.

Do you configure our ERP package?

For packages we carry, such as AFAS, Exact, SAP and Sage, yes: we supply and configure, and whether support stays with us is a separate choice. Process decisions such as ways of working, chart of accounts and approvals stay with you, and the tax and legal review belongs to your accountant or lawyer. For a package we do not carry, we work with the vendor and handle the infrastructure, the devices, the integrations and the data handover.

Related services

Further reading

What an ERP rollout leans on.

Brands

The brands above, one page each

What the brand makes, which lines we supply and what we do around it.

Shall we write out the IT track of your ERP project?

Send us the plan you have now, or the package you have chosen. We will set out next to it what has to happen with environments, accounts, devices, integrations and data, and who does it; if we carry the package, configuration is part of it.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call