ERP Implementation: From Excel and WhatsApp to a Working System
Plan your ERP implementation from workflow mapping to go-live. Follow the key steps for data migration, testing, staff training and a phased rollout.

On this page12 sections
You have bought an ERP system. The login works. There is a dashboard.
But can your staff use it to finish an ordinary customer order without going back to three Excel files and asking the boss what to do?
That is what ERP implementation needs to achieve. It means getting your process, information and people working together in the new system. The software is one part of that job.
Our advice is to start with a manageable part of the business, get it working properly, and then expand. You do not need to change every department on the same day.
Let us follow one customer order
Imagine a small distributor receiving an order for 50 cartons. This is a simple example, not a story about a particular client.
The customer sends Sales a WhatsApp message. Sales prepares a quotation in Excel. The boss approves a special price in another chat. The warehouse checks availability. Finance checks whether the deposit has arrived.
Then the customer asks for 20 cartons first and the remaining 30 next week.
Who knows which price was approved? Who tells the warehouse about the split delivery? Which person remembers that only a deposit has been paid?
If those answers are scattered across messages and files, the team keeps asking the same questions. A useful ERP should make that job easier to follow.
1. Put the actual process on the table
Before choosing dashboard colours, show the developer how that order works today.
Bring the quotation, order sheet, delivery document and payment record. Explain who prepares each item and who approves it.
Then discuss the situations that do not follow the normal route. A customer changes the quantity. Stock is short. The boss is away. A delivery is returned. A staff member entered the wrong item.
These details are part of your business. If nobody explains them at the start, they tend to appear later as “one more small change.”
The aim is to agree on a clear path from enquiry to completed order, including the exceptions that happen regularly.
2. Choose a first phase your team can actually finish
For our distributor, the first phase could cover customer records, quotations, approved orders, deposit status and delivery progress.
That already gives Sales, Finance and the warehouse a shared view of the order. Advanced purchasing, detailed branch stock or a customer portal can follow in later phases.
Write down what belongs in phase one and what is waiting. Also agree on what “finished” means.
For example: “Sales can prepare the quotation, the authorised person can approve the discount, and the warehouse can see which delivery is ready.” That is something the team can test.
“Make our company more digital” is an intention, but it does not tell anyone when the work is complete.
3. Give each decision an owner
The developer can explain options. Your team still needs to confirm how the business should operate.
Who can approve that special price? Is a deposit enough to release the order? Can Sales change a confirmed delivery date without telling the warehouse?
If three people give three different answers, the system cannot solve that disagreement for you.
| Decision | Someone needs to own it |
|---|---|
| What phase one includes | The boss or appointed project lead |
| How each department works | A staff representative who does the job |
| Whether records and balances are correct | The person responsible for that information |
| Whether the agreed process is ready to launch | The authorised business representative |
In a small company, one person may take more than one role. The important thing is knowing whom to ask.

4. Clean the information before moving it
Suppose the customer appears as “ABC Trading” in Sales, “ABC Trading Sdn Bhd” in Finance and “ABC” in the delivery file.
If we import everything without checking, the new ERP may contain three customers instead of one.
This is why moving data costs time. Someone needs to identify duplicates, agree on names and item codes, check opening balances and decide which old records are still needed.
You do not necessarily need every file from the last ten years inside the live system. You might move current customers, active orders and relevant balances, while keeping older documents in an organised archive.
Ask for a sample import first. Open several records and check the details. Confirm totals with the people who know the business. Microsoft also treats migration as work that needs planning, validation and testing.[1]
The file uploading successfully is only the beginning of the check.
5. Build the handovers, then test a real order
Now return to our 50-carton order.
Sales should be able to create it once. Finance should see the deposit status. The warehouse should see the approved delivery instruction. The remaining 30 cartons should still be visible after the first 20 are delivered.
That is more useful than five attractive screens that do not agree with each other.
Where another system is involved, explain the connection in plain terms. Does a payment update the order automatically? Does an invoice go to the accounting system? What happens if the other service is unavailable?
An API is the connection that allows those systems to pass information. Ask who gets alerted when a transfer fails and how staff can put it right.
Then let your own staff test the process. Do not rely only on watching a demonstration.
6. Try the situations that usually cause arguments
A good test session includes an ordinary order, but it also includes the awkward ones:
- The customer changes the quantity after approval.
- A payment arrives late or only covers part of the order.
- A delivery is cancelled or returned.
- Someone clicks the same button twice.
- A staff member tries to view information they should not access.
Record what went wrong, agree who will fix it and try the same task again after the change.
This is often called user acceptance testing. In everyday terms, your team checks whether the system does the job you paid for. Business acceptance, integrations and support readiness are also part of Microsoft's go-live guidance.[2]
A few planned review rounds are much more useful than rushing into launch and discovering a new basic problem every fortnight.
7. Practise the changeover before the busy day
Decide when staff stop updating the old records and start using the new system.
For example, who checks the last delivery in Excel? When is the final data copied across? Who confirms the opening balances on Monday morning?
Keep a backup of the old information and agree on how you would recover if a serious problem stops the launch. Practising that changeover is part of a sensible rollout; Microsoft's cutover guidance recommends rehearsal and clear responsibilities.[3]
Where possible, begin with one team or one agreed workflow. Once it works comfortably, bring in the next group.
You are trying to keep the business running while changing how it works. Choose the launch timing around that reality.
8. Train people using their own daily jobs
Sales should practise preparing quotations. The warehouse should practise deliveries. Finance should practise checking payments and correcting the mistakes it is allowed to correct.
A long presentation does not show whether someone can use the system alone the next morning.
Use familiar examples and short instructions. Let staff ask questions. If everyone struggles with the same button or screen, look at whether the screen needs to be clearer.
Agree on who supports the team after launch, how problems are reported and which hours are covered. Include backups, monitoring and a proper handover of accounts and documentation.
You get what you pay for when these parts are included. A system that is cheap to launch but difficult to use can keep costing the boss time long after the first invoice.

Start with the work your team repeats every day
Bring Haptic X that process. We can help turn it into a practical ERP implementation scope, starting with the part that creates the most daily difficulty. For the money side, read our ERP implementation cost guide.
Sources
Reviewed 1 November 2026. The recommendations adapt general implementation principles to SME planning; they do not imply Microsoft certification or partnership.
[1] Microsoft Learn, Manage configuration and migration data: https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/data-management-configuration-data-migration
[2] Microsoft Learn, Go-live checklist: https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/prepare-go-live-checklist
[3] Microsoft Learn, Cutover process: https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/prepare-go-live-cutover-strategy
Frequently asked questions
01Must we stop using Excel and WhatsApp?
No. They can still help with analysis and communication. The important orders, approvals and balances should have a reliable record, so the business does not depend on finding one old message.
02How long will implementation take?
The scope, data quality and decisions affect the schedule. Ask for milestones you can understand: process agreed, sample data checked, testing completed and launch approved.
03Can we start with one department?
Yes, where the handovers are planned. Check what the other departments still need to send or receive while only part of the business is using the new system.
04Who says the system is ready?
The authorised person in your business, with feedback from the staff who tested it. A developer can show that the software runs; your team must confirm that the agreed work can be completed.
05What should we prepare for the first meeting?
A real example of an order or job, the files used, the people involved and the three biggest daily frustrations. Remove private customer details before sharing.


