ERP implementation in 90 days — realistic playbook
90-day ERP rollouts make great pitches. They rarely happen. What it actually takes when it does happen.
"90-day ERP rollout" is a standard pitch. Sometimes it really happens. More often the timeline slips, and not because the vendor is bad: a 90-day plan assumes conditions that aren't always in place on day one. Here's what those conditions are, how the 90 days are usually split, and where the plan tends to break.
What you need on day zero
- Documented processes. Sales, warehouse, procurement, finance. They don't have to be perfect, but they have to be written down, including who does what.
- One decision maker on the customer side, with authority to settle questions within a day. A committee turns every open question into a week of waiting.
- Clean master data. Items, customers, suppliers, price lists. If the same product exists under several names and codes, cleanup becomes a project of its own before the ERP project can start.
- Willingness to cut nice-to-haves. A fixed deadline only works with flexible scope. Agree in advance what can wait for phase two.
- Key users with time to spare. The people who will work in the system need hours for workshops and testing on top of their normal jobs. If nobody frees up that time, the schedule absorbs the cost.
How the 90 days are usually split
- Audit and gap analysis, about two weeks. Map current processes against the system's standard ones. Every gap gets a decision: change the process, configure the system, or build an extension.
- Configuration and integrations, about four weeks. Set up the chart of accounts, warehouses, document flows, approval rules, user roles. In parallel, build and test the integrations.
- Data migration and testing, about two weeks. Trial loads, reconciliation of balances, end-to-end scenarios from order to invoice to payment.
- Parallel run and fixes, about two weeks. Real transactions in both systems, comparison of results, corrections before the old system is switched off.
That adds up to ten weeks of work. The remaining time is buffer, and it will be used. A plan with no buffer is a best-case scenario, not a 90-day plan.
Integrations are the real trap
The ERP itself rarely blows the timeline. Integrations do: the bank, marketplaces, EDI with large customers, payment gateways, the online store, delivery services, the existing CRM. Each one is a subproject with its own counterpart, its own documentation quality and its own test environment, or the lack of one.
List every integration during the audit, give each an owner, and find out early which external party is slow to respond. For integrations that standard connectors don't cover, a small separate service between the systems is often cleaner than changing the ERP core. That's typical custom web development work, and it keeps the ERP upgradeable.
Common mistakes
- Starting configuration before the processes are agreed, then reconfiguring after every workshop.
- Migrating everything "just in case" instead of opening balances and open documents. Our ERP data migration playbook covers what to move and what to archive.
- Treating training as a one-hour demo the week before go-live.
- Rebuilding the old system screen by screen inside the new one.
- No written go-live criteria, so the decision to switch becomes a matter of mood.
Checklist before you commit to 90 days
- Core processes documented and signed off by the people who run them.
- One decision maker named, with a stand-in for vacations.
- Master data cleanup done or scheduled before configuration starts.
- Full list of integrations, each with an owner and a contact on the other side.
- A written list of what's out of scope for phase one.
- Key users' time blocked in their calendars.
- Go-live criteria agreed: which scenarios must pass, which balances must match.
- Buffer built into the plan, not hoped for.
Ninety days is achievable when the preparation is done. When it isn't, the honest move is a longer plan or a smaller first phase, not a promise that slips three months later.
Planning an ERP rollout or the integrations around one? Reach us on Telegram or MAX.
Got a project on this topic? Tell us the task — we'll come back with an estimate and a schedule.
Message on Telegram → Message on MAX