ERP Installation Process Checklist (Free, Export)

0%

0 of 43 items complete

15 critical items still open - these are the highest-risk gaps.

Download checklist:

1. Implementation agreement and scope

Statement of work names the modules, legal entities, sites and languages in scope, and lists what is explicitly out of scopeCRITICALDeliverables are defined with acceptance criteria (for example fit-gap document, configured test system, trained key users, signed-off UAT)CRITICALResponsibilities are split in writing: what the vendor or partner does, what your team does, what third parties doFixed price, time and materials or capped model is stated, with the change-request process and rates for scope changesCRITICALLicensing (user types, modules, environments) is confirmed against the actual user list before signingData ownership, data protection terms and where the data is hosted are written into the agreementCRITICALWarranty period, defect-fix obligations and post-go-live support hours are definedNamed key people on both sides and a decision-escalation path are listed

2. Environments and installation

Environment plan lists development, test or sandbox, UAT and production, who owns each and how code and configuration move between themCRITICALHardware or cloud sizing is signed off for production (CPU, memory, storage, database edition) against user count and transaction volumeInstallation prerequisites are met: supported operating system, database version, runtime components, ports and certificatesService accounts follow least privilege, with passwords stored in a vault and not in install scriptsTLS certificates are installed and tested for web client, API and any reporting endpointsBackup and restore of the database is configured and a test restore has actually been performedCRITICALMonitoring and alerting cover the application server, database and integration servicesSingle sign-on, identity provider and user provisioning method are configured and tested in a non-production environmentInstallation steps are written down as a runbook so production can be built the same way as testCRITICAL

3. Configuration and data load

Chart of accounts, fiscal calendar, currencies and tax set-up are agreed with finance before transactions are testedCRITICALMaster data owners are named for items, customers, vendors, bills of material and routingsNumber series, posting groups or equivalent defaults are configured and documentedRoles and permissions are mapped from job roles, with segregation-of-duties conflicts reviewedCRITICALData cleansing is done in the source system before extract, with duplicates and inactive records removedTrial data migrations are run at least twice, each with reconciliation of record counts and balancesCRITICALOpening balances (GL, AR, AP, inventory valuation) reconcile to the legacy system on the cut-off dateIntegrations (EDI, banks, shop floor, e-commerce, payroll) have interface specs and test filesCustom code and reports are inventoried, with owners and test cases

4. Application testing and sign-off

Test plan covers end-to-end scenarios (order to cash, procure to pay, plan to produce, record to report), not only single screensCRITICALTest scripts have expected results written before execution, and each is traced to a requirementTesters are business users, not only the implementation teamDefects are logged with severity, owner and retest status; no open critical or high defects at sign-offCRITICALRole-based testing confirms users can do their jobs and cannot do what they should notPerformance test uses realistic volumes (month-end posting, MRP or planning run, large report)Integration tests run against real partner or bank test endpoints where availableRegression test is repeated after every fix package or platform updateWritten UAT sign-off by each process owner is collected and filedCRITICAL

5. Training, cutover and go-live

Key users are trained before UAT and end users before go-live, with quick-reference guides for the top tasksCutover plan lists tasks, owners, durations and dependencies down to the hour, with a rehearsal completedCRITICALFreeze dates for legacy transactions and master data changes are communicatedGo and no-go criteria are agreed in advance and checked at a go-live meetingCRITICALRollback plan exists with a point after which rollback is no longer possibleHypercare roster, support channel and issue triage rules are published before go-liveFirst month-end close is planned with finance, including a review of subledger to GL reconciliationLegacy system access is retained read-only for audit and reference for the agreed period

Tick each item as it is confirmed. Critical items should all be ticked before you move to the next phase. A phase with open critical items is a risk to the schedule, not just a paperwork gap.

Want a second pair of eyes on your ERP project plan?

Optional: send us your phase gates and we will comment on the data migration and testing sections. Not required to use the checklist.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Work through the five groups in order and tick items as you confirm them with evidence, not as you assume them. Items marked critical are the ones that most often cause late surprises: scope boundaries, backups that have never been restored, data reconciliation and written test sign-off. Export the checklist to PDF or Excel and attach it to the project plan so the steering group sees the same status as the project team. Use it again at each phase gate rather than once at the start.

What the implementation agreement must cover

Most disputes in ERP projects trace back to an agreement that was vague about scope or acceptance. The checklist focuses on what is easy to leave out.

Named modules, entities, sites and integrations in scope, and an out-of-scope list
Acceptance criteria for each deliverable, so completion is not a matter of opinion
Split of responsibilities, including who supplies data cleansing and test resources
Change-request process and rates
Data ownership, hosting location and data protection obligations
Warranty period and post-go-live support terms

Installation and environment pitfalls

Whether you install on premises or provision a cloud tenant, the environment plan decides how safely changes move to production. Build production from a written runbook, not from memory, so it matches the tested system. Confirm the supported database and operating system versions for your ERP release before you buy hardware. On premises, check that service accounts, certificates and ports are agreed with IT security early, because these requests often have a lead time of weeks. A restore test of the database is the single most valuable check in this group.

Application testing and sign-off

Application testing is more than clicking through screens. Test whole business scenarios with the people who will run them, write expected results before execution and keep every defect visible until it is closed or formally accepted. Repeat regression tests after each fix package. Collect a signed UAT acceptance from each process owner; this is the document the steering group should see before approving go-live. For test scripts and a defect log, see the related templates linked on this page.

Frequently Asked Questions

What are the main steps in an ERP installation process?

Typically: agree scope and the implementation agreement, plan and build environments, install and configure the software, load and reconcile data, test the application with business users, train people, cut over and support the first weeks after go-live.

Is this checklist only for Microsoft ERP?

The phases apply to any ERP. Environment details differ, for example Business Central on premises needs a service tier and SQL Server while a cloud tenant is provisioned in an admin center, but scope, data, testing and cutover tasks are the same.

What should an ERP application testing checklist include?

End-to-end scenarios, role-based access tests, integration tests, performance with realistic volumes, a defect log with severity, regression after fixes, and a written sign-off by each process owner before go-live is approved.

How long does ERP installation and implementation take?

The software install itself may take days, but a full implementation for a small or mid-size manufacturer commonly runs several months. Data migration and testing, not installation, usually decide the schedule.

If you want an ERP assistant that answers questions from your live data on your own servers after go-live, Netray can add a private AI layer on top of the system you install. The checklist works without it.

Talk to an Expert Explore More Free Tools

Related Tools

ERP Migration & Selection

More ERP Migration & Selection tools

See all

ERP Installation Process Checklist

0 of 43 items complete

1. Implementation agreement and scope

2. Environments and installation

3. Configuration and data load

4. Application testing and sign-off

5. Training, cutover and go-live

Want a second pair of eyes on your ERP project plan?

How to use the checklist

What the implementation agreement must cover

Installation and environment pitfalls

Application testing and sign-off

Frequently Asked Questions

What are the main steps in an ERP installation process?

Is this checklist only for Microsoft ERP?

What should an ERP application testing checklist include?

How long does ERP installation and implementation take?

Related Tools

ERP UAT Test Script Template

ERP Cutover Weekend Readiness Checklist

ERP UAT Defect Log Worksheet

ERP Implementation Risk Register Template

Business Central Go-Live Readiness Checklist

More ERP Migration & Selection tools

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Troubleshooting