Share this
by Drew Reedy on October 13, 2026
Implementing a new ERP sounds like a daunting task. Moving operating systems into new software takes time and resources, but proper planning and preparation make all the difference. And in the end, your team has connected workflows and integrated data that speed daily operations and improve business outcomes.
For manufacturers, a successful ERP implementation depends on accurate master data, good communication and collaboration, and well-rounded training and support.
What should your team expect? How much time should employees set aside? What needs to happen before go-live? This guide answers those questions, with practical input from a QT9 ERP implementation specialist, including common customer challenges, frequently overlooked capabilities and preparation that supports confident daily use.
Contents
What is the typical ERP implementation process?
How long does ERP implementation take?
Assembling an ERP implementation team
What are common ERP implementation challenges?
How to prepare data for ERP implementation
What training must take place before ERP implementation?
What does an ERP go-live plan entail?
What is QT9 ERPs implementation process?
What is ERP implementation?
ERP implementation is the process of preparing and introducing enterprise resource planning software into a business. It includes planning, system setup, data migration, employee training, testing, go-live and post-launch support.
In manufacturing, ERP implementation establishes how purchasing, inventory, production, sales, shipping and accounting work together in the system. That includes the information each department enters, the decisions employees make and the transactions that move work forward.
For example, completing a production job affects finished goods inventory and production costs. Implementation prepares production and accounting teams to understand and verify those connected results.
What is the typical ERP implementation process?
An ERP implementation typically covers several common stages: site and project planning, data and system configuration, training, testing and go-live. The processes often overlap as data and operations are transitioned and teams refine their knowledge.
How long does ERP implementation take?
ERP implementation timeframes are driven by scope, data readiness, workflows and, often, employee availability. Industry sources cite implementation timelines ranging from a few months for smaller businesses to years for large, international organizations.
Take the first step by building a timeline around defined milestones:
-
Data prepared and verified
-
Major process decisions resolved
-
Users trained and given practice time
-
Connected workflows tested
-
Opening balances and open transactions prepared
-
Go-live responsibilities approved
A realistic schedule also accounts for current and upcoming production demands, physical inventory and accounting deadlines. If the same employees are managing implementation alongside their regular responsibilities, their availability needs to be reflected in the plan.
Assembling an ERP implementation team
An ERP implementation team should include an executive sponsor, an internal project lead and subject matter experts from the departments that will use the system. For manufacturers, those departments typically include purchasing, accounting, inventory management, production, shipping and sales, with IT and quality involved where relevant.
The executive sponsor should plan and resolve competing priorities. The project lead serves as the main contact with the ERP vendor, coordinates training with department leads, and manages project tasks and timelines. Department representatives prepare data, make process decisions, ensure employees get proper training and practice, and verify that workflows and users are ready for go-live.
What are common ERP implementation challenges?
Some of the most common ERP implementation challenges our ERP implementation team sees include underestimating employee time commitment, incomplete data, leaving processes undefined and involving users too late in the process.
Time commitment
Most often, managing ERP implementation requires process testing and training sessions that occur in between normal, everyday work. Teams need to dedicate time for data cleanup, testing, well-thought-out decisions and practice.
It’s a good idea to build that time into the project plan and agree ahead of time on how regular responsibilities will be covered during the process.
Undocumented processes
Some workflows are not documented and are performed manually based on legacy knowledge. Implementing ERP software can bring those unwritten workflows into view.
This is a good time to get daily users involved in decision-making. Document who does what, what information they need and how processes are handled. Resolve issues before workflows are turned into new system habits.
Human nature tends to favor routine. But needs and tools evolve, and a familiar process may include steps that no longer serve a useful purpose. Ask what each step accomplishes and whether the ERP’s standard workflow supports that requirement. Evaluate the business need before trying to reproduce every detail of the previous approach.
Resistance to change
Employees may hesitate to adopt a new ERP because they are comfortable with familiar routines, uncertain about changing responsibilities or concerned about learning the system while keeping up with daily work. Explain the reasons for the change and what it means for each department. Involve employees early, listen to their concerns and provide time for hands-on practice. Department leaders should reinforce agreed workflows and help employees address difficulties as they arise.
Limited buy-in
Leadership may select the ERP, but employees determine how consistently it is used. Keep those lines of communication open to allay employee fears. Explain why processes are changing, involve users in relevant decisions and give them time to practice. Company-wide adoption begins during implementation.
Training without practice
Watching a process demonstrated does not establish the ability to complete it independently. Have users work through their responsibilities, record questions and return for clarification. This reveals gaps while the implementation team is still preparing for launch.
How to prepare data for ERP implementation
Manufacturers should prioritize the preparation of records that are the most necessary for daily business and which influence transactions across multiple areas. This generally includes product data, supplier/vendor data, customer data, inventory, employee and accounting/financial information.
Data Area |
What to Review |
Product/Item Master Data |
Naming conventions, units of measure, part numbers, descriptions, Delete obsolete items. |
Supplier/Vendor Data |
Names, tax IDs, contacts, lead times; Consolidate duplicates. Delete obsolete. |
Customer Data |
Names, addresses, contacts, account history, credit limits, payment terms |
Inventory Data |
Quantities on hand, locations, lot or serial numbers, statuses |
Employee Data |
Names, IDs, job titles, pay rates. Remove terminated employees. |
Accounting & Financial Data |
COA, AR, AP, balances, active budgets; Ensure historical balances match. |
Data preparation best practices
-
Review and clean records early. Remove duplicates, correct errors and complete missing information before migration. Standardize item names, units of measure and other shared fields to support consistent transactions and reporting.
-
Map data to the new ERP. Document where existing information belongs in the new system, including any required format changes. Confirm that fields carry the same meaning in both systems.
-
Assign ongoing ownership. Identify who is responsible for maintaining each type of master data and who can create, change or approve records. Clear responsibilities help preserve data quality after launch.
-
Test before the final transfer. Run trial migrations in a test environment, then have department representatives check the imported records and use them in representative transactions. Resolve errors and repeat testing before go-live.
What training must take place before ERP implementation?
ERP training usually combines role-specific instruction, hands-on practice and follow-up using representative business scenarios. Employees should practice with their own items, suppliers, BOMs and transactions whenever possible.
A practical training cycle is:
-
Learn a workflow with the implementation specialist.
-
Complete the workflow independently in a practice environment.
-
Record questions and unexpected results.
-
Review those questions and repeat the exercise.
Ensure training includes the handoff to the next step in the workflow. Receiving employees, for example, should understand how their entries affect available inventory and the information accounting reviews.
Recorded training sessions provide a useful refresher, while independent practice can uncover where more explanation is needed.
What does an ERP go-live plan entail?
An ERP go-live plan should define final data migration, physical inventory, open transactions, user access, support coverage and launch approval. Each activity needs an owner and a scheduled completion point.
For manufacturers, the plan should address:
-
Inventory: How opening quantities will be established and movements controlled during the transition.
-
Open orders: How purchase orders and sales orders will be transferred and verified.
-
Production jobs: How unfinished work and its associated information will carry forward.
-
Accounting: How balances and transaction cutoffs will be checked.
-
User readiness: Whether employees have the access, equipment and training required.
-
Support: Who answers questions and handles urgent issues.
-
Launch approval: Who decides whether readiness conditions have been met.
Walk through the transition with everyone responsible for an activity. A shared review helps uncover dependencies before go-live week.
Testing your ERP system before go-live
Your go-live plan should include testing the system by running representative business scenarios across departments and verifying the resulting inventory, production and financial records. Include everyday work and relevant exceptions.
Consider a “day in the life” dry run. Use questions such as:
-
Can purchasing process the required purchase orders?
-
Can receiving record today’s incoming materials?
-
Can production complete its work through the shop floor system?
-
Can shipping process customer orders?
-
Can accounting verify the resulting activity?
Test partial receipts, shortages, changed orders and rework where applicable. For each scenario, document the expected result, actual result, issue owner and retest outcome. Give unresolved issues a clear disposition before approving launch.
If parallel processing is planned, define its purpose, duration and reconciliation responsibilities. Employees need to know which system controls live transactions during the transition.
After ERP go-live
After your ERP is officially implemented, ensure your teams have support for user questions, data checks and initial business cycles, such as month-end close. This stabilization period helps employees establish reliable routines.
-
Review issues regularly, assign owners and distinguish between training questions, data corrections and process decisions.
-
Keep process owners involved. Their role continues as employees encounter situations that did not arise during testing.
-
Use the business goals established at the beginning of implementation to guide subsequent improvement. Review whether teams can obtain the information and complete the work the project was intended to support.
What is QT9 ERP's implementation process?
QT9 supports ERP implementation through project coordination, process-focused training, data migration guidance, workflow testing and go-live support. Its implementation team brings experience across manufacturing, supply chain, accounting and project management. A customer project page organizes timelines, tasks, meeting information and documented decisions.
QT9 Implementation Specialists work directly with customer teams to teach the system in the context of their daily responsibilities. Customers practice with their own items, BOMs and suppliers, then bring questions back for review. Training sessions are recorded and transcribed for later reference.
QT9 also provides a 45-day Hypercare period after go-live, supporting customers as they settle into new workflows, address questions and assist with activities, such as their first accounting month-end.
Explore QT9 ERP implementation services to discuss the preparation, responsibilities and support your manufacturing operation needs.
