Part of our guide hub: ERP software
The ERP implementation process is where projects succeed or quietly fail, long before anyone judges the software itself. Two businesses can buy the same system and get opposite results, because one cleaned its data, appointed an owner and rolled out in phases, while the other bought every module, migrated years of errors and trained staff the week after go live.
This guide walks through each phase, what has to be finished before the next begins, how long each usually takes, and the failure patterns that appear again and again in Pakistan.
ERP implementation step 1: discovery and process mapping
The first phase documents how the business actually works, not how the manual says it works. Walk the floor: how does a purchase order really get approved, who writes the gate pass, what happens when a customer returns damaged goods.
Output of this phase is a written process map, a list of required reports, an integration list and a scope for phase one. Skipping it is the single most expensive shortcut in the whole ERP implementation process.
Step 2: scope, phasing and the project team
Next, decide what phase one includes and, more importantly, what it excludes. Most successful rollouts start with the department in most pain, usually inventory, sales or accounts, and add production, HR and payroll later.
Name an internal project owner with authority to make decisions, plus a key user from each department. Without that, every small question waits for a meeting and the timeline slips by weeks.
ERP implementation step 3: data cleaning and migration
This phase surprises everyone. Item codes duplicated across branches, three spellings of the same customer, opening balances that do not reconcile, stock counts that were never verified. Migrating that as is produces a new system nobody trusts within a month.
- Agree one master item list with clean codes, units and categories.
- Deduplicate customers and suppliers, and standardise names.
- Reconcile opening balances with the accountant before import.
- Do a full physical stock take immediately before go live.
- Import into a test environment first and check totals against the old system.
Who does what during ERP implementation
Confusion about responsibility causes more delay than any technical problem, so write the split down before the project starts. The vendor typically leads process mapping workshops, configures the system, builds custom reports and integrations, trains users and supports go live. Your team owns decisions, supplies clean master data, tests with real transactions, approves each phase and enforces the new process once it is live.
Two roles are worth naming explicitly. The internal project owner decides when a request is in scope or a phase two item, which protects the budget. The data owner is accountable for item codes, customer records and opening balances being correct before migration, and that single appointment removes the most common cause of a failed ERP implementation process.
Integrations with systems you already run
Most businesses do not start from nothing. There is usually a POS in the shops, an online store, an attendance machine, courier portals and an accountant with years of ledgers. Decide early which of these the ERP replaces and which it connects to, because that decision changes both scope and cost.
Integration work also needs test data and a plan for failures: what happens when the courier service is unreachable, or when a POS terminal syncs a sale twice. Agreeing those rules during configuration is far cheaper than discovering them in the first week after launch.
Step 4: configuration and customisation
Now the system is shaped to the mapped process: chart of accounts, tax rules, document formats, approval workflows, user roles and permissions. Custom reports and any development work happen here.
Guard the scope carefully. Every department will ask for its old screen to be recreated, and that is how budgets double. The rule that works is simple: match the standard system unless a difference costs money or breaks compliance.
ERP implementation step 5: testing real scenarios
Test with your own transactions rather than sample data. Run a purchase with partial delivery, a sales return, a stock transfer between branches, a credit customer payment, a month end close and the reports your auditor asks for.
Key users should run these tests themselves, because the people who will use the system daily find problems that vendors never will.
Step 6: training before go live
Train by role in the two weeks before launch, not after it. A storekeeper needs three screens and a scanner; the accounts team needs vouchers, tax and reconciliation; management needs dashboards. Give each group short sessions with their own data, and leave printed guides at their desks.
Plan refresher sessions a month later. By then everyone has questions they did not know to ask on day one.
ERP implementation step 7: go live and parallel running
Go live on a quiet day, never at month end or before a season peak. Many businesses run the old and new systems in parallel for a short period, which is safer but doubles workload, so keep the parallel window short and defined.
Keep the implementation team physically present for the first days. Problems solved on the spot stop staff from inventing workarounds that outlive the project.
Step 8: support, review and phase two
After stabilisation, review what worked: which reports are actually opened, where staff still keep side registers, which approvals slow things down. Fix those before starting phase two, and only then add the next modules.
A realistic ERP implementation process never truly ends. Businesses change, and the system should change with them, which is why a small maintenance budget matters.
How long the ERP implementation process takes
| Phase | Typical duration | Who leads |
|---|---|---|
| Discovery and mapping | 2 to 4 weeks | Vendor with your key users |
| Data cleaning | 2 to 6 weeks, often the longest | Your team |
| Configuration | 3 to 6 weeks | Vendor |
| Testing | 2 to 3 weeks | Your key users |
| Training | 1 to 2 weeks | Vendor and internal owner |
| Go live and stabilisation | 2 to 4 weeks | Both |
Timelines stretch mainly for two reasons: unclean data and slow decisions, not slow developers.
Why the ERP implementation process fails
- No internal owner, so decisions wait and the vendor guesses.
- Big bang launches across every department at once.
- Dirty data migrated because cleaning felt boring.
- Scope creep from recreating every old habit as a customisation.
- Training treated as optional, producing parallel registers in spreadsheets.
- No management pressure to stop using the old process.
Signs the rollout is going wrong early
An ERP implementation process rarely fails suddenly. Problems announce themselves weeks before anyone admits the project is late. Watch for four signals. First, decisions that stay open for more than a few days, which usually means nobody has real authority. Second, key users who miss testing sessions because operations are busy, which guarantees that faults appear after go live instead. Third, a growing list of small customisations, each described as tiny, which together push the timeline out by a month. Fourth, master data that is still being corrected in the week before launch.
Any of these is fixable if raised early. The usual remedies are to cut phase one scope, freeze customisation requests until after launch, and formally free up two or three key users for the testing period. Projects that stop and fix these issues finish late by weeks; projects that ignore them finish late by quarters, or never finish at all.
After go live: measuring whether it worked
The ERP implementation process only ends when the results are measured. Agree the measures before launch so the review is honest. Useful ones include how long it takes to close the month, how often stock in the system matches a physical count, how many orders are entered twice, and how quickly management can see yesterday’s sales. Compare them with the old process at one month and three months.
Also watch the quiet indicator: whether staff still keep private registers. If a storekeeper maintains a notebook beside the system, something in the process does not fit yet, and that is worth fixing before adding new modules.
Compliance work inside the rollout
Sales tax invoices, withholding, and in some sectors digital invoicing integration all need configuring and testing before go live. Rules change from time to time, so verify the current requirements at fbr.gov.pk and agree who maintains compliance updates after launch.
What to agree with the vendor in writing
- Scope for phase one, with a written exclusion list.
- Number of implementation days included, and the rate beyond them.
- Who performs data migration and how it is verified.
- Training days by role, and refresher sessions.
- Support hours, response times and escalation after go live.
- Data ownership and how you export everything if you leave.
Our guides to ERP software price in Pakistan and choosing the best ERP software in Pakistan cover the commercial and selection side of the same decision.
Frequently asked questions
How long does the ERP implementation process take?
Phase one commonly runs three to four months from discovery to stabilisation. Full multi department rollouts take longer, and data cleaning is usually the longest single task.
Should we go live with all modules at once?
Rarely. Phased rollouts reduce risk, spread cost and let staff absorb change, which is why most successful projects start with one department.
Who should lead the project internally?
Someone with authority to decide and time freed from other duties, usually an operations or finance manager supported by key users from each department.
What is the most common cause of delay?
Unclean master data and slow internal decisions. Both are inside your control, which is the encouraging part.
The bottom line
A sound ERP implementation process is mostly preparation: map the real process, clean the data, phase the rollout, train before launch and keep scope under control. Software quality matters, but discipline decides the outcome. If you want a phased plan for your own business, see our ERP development services or contact our team.