ERP Implementation Phases and Timeline for Small Businesses

An ERP implementation for a small business runs through five stages: discover what the business needs, define the scope and plan, build and configure, prepare for go-live with testing, training and data migration, then operate and improve. Microsoft's Success by Design framework for Dynamics 365 names these Discover, Initiate, Implement, Prepare and Operate. No vendor publishes a standard duration, so your timeline has to be built from your own scope, which this article shows how to do.

Who this is for

This is for owners, finance leads and IT managers at small businesses who are about to select or start an ERP such as Business Central or ERPNext and want to know what the stages are and what should be finished at the end of each. At the end you will have a phase-by-phase checklist, a way to estimate a timeline from your scope, and a list of things that commonly go wrong at cutover.

The phase model comes from Microsoft's Dynamics 365 implementation guidance, and the test-then-live approach from the ERPNext documentation; both pages were checked on 26 October 2026. Other products and implementation partners use their own names and templates. The structure carries over, but the details do not.

The five phases at a glance

The purposes follow Microsoft's Success by Design page; the "what should exist" column for Discover, Initiate and Implement is a practical summary rather than Microsoft's wording. Microsoft says the phases are methodology-agnostic, so they fit an agile, waterfall or hybrid plan.

Phase 1: Discover

Discovery is where you decide what the ERP must do before you configure anything. Microsoft describes this phase as gathering and validating business requirements and finalizing the high-level solution approach, including an environment strategy and an organizational strategy.

For a small business, do the following:

1. List your processes. Order to cash, procure to pay, inventory, month-end close, payroll hand-off, tax filing. Note who does each step today and in which tool (often a spreadsheet and accounting package).
2. Separate must-haves from nice-to-haves. Your first release should cover the must-haves only.
3. Inventory your data. Customers, vendors, items, chart of accounts, open invoices, opening stock, fixed assets. Note where each lives and how clean it is.
4. List integrations. Banks, payment gateways, e-commerce, payroll, e-invoicing or tax portals. For one common pattern, see ERP and e-commerce sync with polling, webhooks and queues.
5. Name the owners. A project sponsor, a day-to-day project lead from the business, and a process owner for each area. Partners configure the system; only your staff can say what the process should be.

If you are still choosing a product, ERPNext vs Odoo for a small manufacturer and Business Central pricing: Essentials vs Premium cover two comparisons.

Phase 2: Initiate

In Microsoft's framework, the Initiate phase is where the team defines all in-scope workstreams and updates the project plan. Microsoft says the Solution Blueprint Review is the starting point of Success by Design and recommends making it mandatory for the project. The current page says the review should begin in Discover, once the high-level approach and key workstreams are taking shape, rather than being deferred to Initiate.

You do not need Microsoft's formal reviews to benefit from the idea: have someone who did not write the design challenge it before you build.

Outputs for a small project:

• A written scope statement naming the modules, companies or legal entities, locations and users in the first release, and what is deferred.
• A project plan with milestones for build, data migration, testing, training and cutover.
• A decision on licenses and environments (production plus at least one place to test).
• A risk list: data quality, key people availability, integrations, customizations.

Control customizations early

Every customization adds testing and upgrade work. Microsoft's guidance says the cloud service itself is Microsoft's responsibility for reliability and performance, but that solution design, configurations, customizations and partner solutions can affect overall performance. Treat each custom requirement as a cost to justify.

Phase 3: Implement

Per Microsoft, Implement is where the team builds the solution according to the agreed design and scope. Success by Design adds Implementation Reviews in this phase, which look more deeply at the data model, security, integrations, application lifecycle management and testing strategy. For a small business, that translates to a short list of build tasks:

1. Foundations first. Company, fiscal year, chart of accounts, currencies, tax setup, users and roles. ERPNext's guidance is to configure foundations before importing day-to-day transactions, and warns that changes to currencies, account structures or stock rules later can be disruptive.
2. Master data. Customers, vendors, items, price lists, warehouses.
3. Process configuration. Numbering, approvals, documents and print formats, tax invoices.
4. Integrations and reports. Build and test each integration against test credentials.
5. Security. Give each role the least access it needs. In Business Central, license types limit what a user can reach regardless of permissions; see Business Central Team Member license.

Migrate data in trial runs

Do not leave data migration to the last week. In Business Central, Microsoft's documentation describes data migration wizards for supported sources (Microsoft's page names Dynamics GP, Dynamics NAV and QuickBooks) and configuration packages for other sources, which can be imported from Excel or a .rapidstart file. Microsoft says configuration packages are for setting up a company for the first time, not for companies already in production, and that importing large amounts of data through them can affect performance. In ERPNext, the documentation names the Data Import tool for masters and opening balances.

Practical rules that apply to any ERP:

• Migrate in dependency order: setup tables first, then masters, then opening balances.
• Clean the source data before import: duplicates, inactive customers, items with no unit of measure.
• Reconcile after each trial load: the totals in the ERP should agree with the source for receivables, payables, bank balances and stock value.
• Repeat the load until it is boring. Each trial run should be faster and cleaner than the last.

Phase 4: Prepare

Microsoft describes Prepare as the point where the solution has been built and tested and the team is preparing for the final round of user acceptance testing (UAT) and training. By then the team should have the customer approvals, information security reviews, a cutover plan with go/no-go criteria, scheduled mock go-lives, a ready support model, and a deployment runbook with tasks, owners, durations and dependencies. Success by Design then uses a Go-live Readiness Review to find remaining gaps, and Microsoft makes that review mandatory.

Test like it is a normal month

The ERPNext documentation gives a clear test standard: run a complete sales, purchase, stock and accounting cycle before going live, test with the same user access your team will have, and check opening receivables, payables, bank balances, stock quantities and values, fixed assets, taxes and the trial balance. Have real users complete their most common tasks, not just the project team.

A useful test script follows one transaction of each kind through its whole life:

Quote -> sales order -> delivery -> invoice -> receipt -> bank reconciliation
Purchase request -> purchase order -> goods receipt -> vendor invoice -> payment
Stock adjustment -> stock valuation report -> month-end close -> tax return data

Train by role

Train each role on its own tasks, in the test system, using the real documents it handles. Short sessions close to go-live work better than long ones early on, and each trainee should complete a task unaided.

Plan the cutover

Write the cutover as a runbook with owners and times:

1. Freeze changes in the old system at an agreed time.
2. Load final opening balances and open items. ERPNext's advice is to move only the data needed to operate and report from the cutover date.
3. Reconcile every opening balance to the old system.
4. Confirm go/no-go criteria with the sponsor.
5. Open the new system to users.
6. Keep the old system available for historical reporting, as ERPNext recommends.

Do a mock cutover at least once. It finds timing and permission problems while they are cheap to fix.

Phase 5: Operate

In the Operate phase the solution is live. Microsoft says the goal is stabilization and a shift in focus to functionality and enhancements planned for the next phase of the project.

In the first weeks:

• Hold a daily short check-in for questions and issues, and log every one.
• Watch the first period-end close closely, and compare reports with the old system if you ran in parallel.
• Introduce additional modules in controlled phases, in line with the ERPNext guidance, rather than adding everything at once.
• Review user licenses and roles. If people are under- or over-licensed, adjust before the next renewal.

Building a timeline from your scope

Because Microsoft and the ERPNext documentation do not give a duration, estimate from scope. Work backwards from the date you must go live, and choose a date that is not in a period-end, stock-take or tax filing window.

A practical method:

1. Give every phase a list of tasks and owners.
2. Mark the tasks that depend on your staff, and check their calendars.
3. Add at least two full data-migration trial loads and one mock cutover.
4. Add a buffer for rework after UAT.
5. Fix the go-live date last, and move it if the go/no-go criteria are not met.

Troubleshooting common problems

Checklist

• Requirements, owners and data inventory written down.
• Scope for the first release signed off, with a deferred list.
• Foundations (company, chart of accounts, currencies, taxes) configured before transactions.
• At least two data-migration trial loads reconciled.
• A full sales, purchase, stock and accounting cycle tested by real users.
• Training done by role, with a task each trainee completes.
• Cutover runbook with go/no-go criteria and one mock run.
• Old system kept available for historical reporting.
• Support routine and first month-end close planned.

References

• Introduction to the Success by Design framework (Microsoft Learn): https://learn.microsoft.com/en-us/dynamics365/guidance/implementation-guide/success-by-design
• ERPNext implementation strategy (Frappe documentation): https://docs.frappe.io/erpnext/user/manual/en/implementation-strategy
• Apply company configuration packages (Business Central): https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/administration/apply-company-configuration-packages
• Import business data from other finance systems (Business Central): https://learn.microsoft.com/en-us/dynamics365/business-central/across-import-data-configuration-packages