“How long until we’re live?” is the second question every operations lead asks, right after cost. The honest answer for a small-to-mid deployment is about 90 days — an 8 to 12 week roadmap. Here is what actually happens in each phase, and what moves the date.
Phase 1 — Extraction (Days 1–30)
The first month is discovery and groundwork, not configuration. We run a technical audit of your current systems, harden the single-tenant VPC on Google Cloud with Terraform, and begin ingesting legacy data.
The schedule driver here is almost always data quality, not technology. Clean, well-structured exports move fast; a decade of inconsistent records in a legacy NetSuite or QuickBooks instance takes longer to map and validate. Spending real time here is what makes the cutover boring — which is the goal.
Phase 2 — Injection (Days 31–60)
The second month is where the system takes shape: ERP core deployment, configuration of the modules you actually use (accounting, inventory, manufacturing, CRM), Terraform stabilization, and grounding any AI models on your real historical data.
The driver here is scope discipline. Every “while we’re at it” customization is a schedule risk. We deploy the standard, proven workflows first and treat bespoke logic as a deliberate, separately-scoped decision rather than a default.
Phase 3 — Activation (Days 61–90)
The final month is go-live: production cutover, user onboarding, and launching any automation or digital-workforce agents. Because the data work happened in Phase 1, the cutover itself is a controlled event, not a leap of faith.
The driver here is people, not software — training, change management, and getting every team comfortable before the old system is retired.
What makes a deployment slip
In practice, timelines move for a short list of reasons:
- Messy source data that needs heavy cleansing before it can be mapped.
- Scope creep — custom features added mid-flight instead of after stabilization.
- Slow decisions on the client side: approvals, access, and sign-offs that stall a phase.
- Heavy compliance requirements (for example FDA 21 CFR Part 11 or ISO 13485), which add validation steps — planned for, but real.
How to keep it on schedule
The single biggest lever is starting the data conversation early and keeping the first deployment standard. Own the platform first; customize second. That sequencing is why most of our deployments land inside the 90-day window.
If you want a timeline mapped to your specific systems and headcount, a free architecture review produces a phased 90-day plan and a TCO comparison. The ERPNext FAQ covers the related cost and ownership questions.