Manufacturing
Choosing an ERP for an injection molding plant without losing history
By SourceX Editorial · Updated
Short answer
Choosing an ERP for an injection molding plant means testing it on molding work: family molds and cavitation, mold and press tracking, versioned process sheets, resin and colorant lot traceability, regrind and MES links. Plan history at the same time: migrate masters and open orders, and archive full transaction history in a readable export before the old system goes.
Key takeaways
- Run vendor demos on your own hardest parts, such as a family mold with a blocked cavity, not on a generic sample.
- Molds deserve to be treated as tracked assets, with shot counts, maintenance and ownership recorded.
- Process sheet versions linked to lots are the history molders most often lose in a switch.
- Migrate masters and open transactions; archive closed transactions in full with an old-to-new ID crosswalk.
- Ask how complete the new and old systems' exports are before signing, not at exit.
What should a molder's ERP handle that a generic ERP may not?#
A molder's ERP should handle the ways molding breaks generic manufacturing assumptions. One mold can make several different parts in one shot, a cavity can be blocked for repair, the same part can run on several presses with different cycle times, and material is consumed as resin, colorant and regrind rather than as discrete components.
Molds also behave like both tooling and assets. They have shot counts, maintenance intervals, storage locations and, very often, an owner who is not the molder. A system that treats a mold as a simple resource loses most of that history.
- Family molds and multi-cavity tools, with cavity blocking and its effect on yield.
- Mold and press compatibility, including tonnage, shot size and auxiliary equipment.
- Resin, colorant and masterbatch lots, with regrind ratios and drying records.
- Secondary operations such as inserts, pad printing, welding and assembly.
- Customer-owned tooling, with ownership and storage status per mold.
- Quality documentation such as first article and production part approval packages.
Selection checklist: what to test in the demo#
The selection checklist below turns molding needs into demo tests. Ask each vendor to run them with your data, and note how each capability will store history, since that decides what you can trace later.
| Capability | What to test in the demo | Why it matters for history |
|---|---|---|
| Mold master and shot counter | Record shots from production and trigger maintenance | Builds mold life and repair history |
| Press scheduling with mold constraints | Schedule a family mold on two eligible presses | Keeps planned versus actual by press |
| Process sheets with version control | Change a setting and show which lots used each version | Links process changes to outcomes |
| Resin and colorant lot genealogy | Trace a shipped lot back to resin lots and regrind | Supports complaints and recalls |
| Scrap and downtime from the MES | Pull reason codes and counts from the press | Keeps causes, not just totals |
| Quality records | Attach first article results and holds to a lot | Connects defects to dispositions |
| Customer-owned tooling register | Show owner, location and release history per mold | Avoids tooling disputes |
| Data export | Export every table with custom fields and attachments | Protects history at the next switch |
- 01Your work records
- 02Personal details removed
- 03You approve the release
- 04Licensed to AI developers
Process sheets: the history molders most often lose#
Process sheets are the history molders most often lose because they rarely live in the ERP. Setup sheets sit in binders at the press, in Excel files on a process engineer's drive or in the press controller itself, and changes are made on the floor with a pen.
The new system, or the MES connected to it, should store each process sheet as a controlled document with a version, an effective date and a reason for change, and record which version ran on each production order. That link is what lets an engineer explain why a sink mark problem appeared in one month and disappeared the next.
Before the switch, gather the current sheet for every active mold and the older versions you can find. Even an incomplete archive of past settings is better than starting the new system with no history at all.
The history plan: migrate masters, archive transactions#
The history plan splits records into what the new ERP needs to operate and what the company needs to keep. Masters and open transactions migrate. Closed transactions go to a complete, documented archive, linked to the new system by a crosswalk of old and new IDs for items, molds, customers and suppliers.
Do not assume any export is complete. Oracle's NetSuite help, for example, says its Full CSV Export does not currently export all data, covering lists such as customers, items and vendors plus the transaction detail report. Whatever your current system, test the export against record counts before you rely on it.
| Record | Migrate | Archive |
|---|---|---|
| Items, BOMs and routings | Yes, cleaned | Prior revisions |
| Mold masters and shot counts | Yes | Maintenance history |
| Customers and suppliers | Active ones | All |
| Open sales and purchase orders | Yes | Not needed |
| Closed sales and production orders | No | Yes, in full |
| Lot genealogy and resin lots | Open lots | Yes, in full |
| Quality records and NCRs | Open items | Yes, in full |
| Process sheets | Current versions | All versions found |
Illustrative: a custom molder picks an ERP#
Illustrative: a fictional custom injection molder serving automotive and appliance customers runs an older on-premise ERP, keeps setup sheets in Excel and collects cycle and downtime data through a press monitoring system. Mold ownership is tracked on a whiteboard in the tool room.
The owner and IT lead shortlist vendors and send each one a script: schedule a family mold with a blocked cavity, trace a shipped lot back to resin and regrind, and change a process sheet with a reason. Only some vendors complete the script with the molder's own data, which narrows the field quickly.
For history, the team migrates masters and open orders, builds a mold register with ownership per tool, and archives closed orders, lot genealogy and NCRs from the old database with a crosswalk. Later, a customer complaint on a part made before the switch is traced in the archive without restoring the old system.
Questions to ask ERP vendors about exports and exit#
Questions about exports and exit belong in the selection process, because the ERP you choose today is the legacy system of a future switch. Vendors answer these more carefully before a contract is signed than after.
Get the answers in writing and attach them to the contract or the statement of work. A demo of a full export, run on test data, is worth more than a feature list.
| Question | Good answer | Red flag |
|---|---|---|
| Can we export every table, including custom fields? | Yes, self-service, documented | Only through saved reports |
| Are attachments and document links included? | Yes, with an index to records | Files only, no record links |
| Is API or database access included in our plan? | Included, with documented limits | Extra fee decided later |
| What happens to our data after we leave? | Defined window to export, then deletion | No written terms |
| Can process sheet versions and lot genealogy be exported? | Yes, with history intact | Current version only |
Where licensing fits for molding records#
Licensing fits after the archive exists, not before. A complete, documented history of quotes, production orders, process changes, scrap and downtime, and quality decisions is the same asset a molder would review if it later considers licensing operating records.
Customer part designs, mold designs owned by customers and customer pricing stay out. SourceX reviews such records through the SourceX five-step transaction, starting with a metadata-only fit check, and the molder approves every scope before anything is delivered.
Frequently asked questions
Should we choose an ERP with built-in MES or connect a separate MES?
Either can work. Built-in modules reduce integration work, while a separate MES may handle press monitoring and process data in more depth. What matters for history is that scrap, downtime and process sheet versions are stored with production orders and can be exported.
How much history should go into the new ERP?
Usually only masters, open transactions and the recent history people use daily. Loading years of closed transactions often means forcing old records into new structures. A complete archive with a crosswalk keeps the history without slowing the implementation.
Who owns the molds recorded in our ERP?
Often the customer, depending on tooling quotes, invoices and agreements. The ERP should record ownership per mold, not assume it. Customer-owned molds and their designs are usually excluded from any outside use of records.
Can old process sheets be migrated?
Current sheets for active molds should be loaded as controlled documents in the new system or MES. Older versions can be archived as files linked to the mold and date range they applied to, even if they never enter the new system.
What if our current ERP vendor is changing its on-premise strategy?
Treat it as a prompt to plan exports early. An Epicor post on the EpiUsers forum titled Epicor Kinetic Innovation Moves to the Cloud: On-Premises Development Ends in 2028 describes export options for data and attachments. Whatever your vendor, confirm export methods before deadlines arrive.
Sources
- Oracle's NetSuite help says the Full CSV Export does not currently export all data; it covers accounting lists, classes, contacts, customers, departments, employees, items, notes, partners, saved reports you own, tasks, the transaction detail report and vendors. Source
- An Epicor post on the EpiUsers forum, titled 'Epicor Kinetic Innovation Moves to the Cloud: On-Premises Development Ends in 2028', says Epicor is outlining export options (data plus attachments) and which exports can be automated through APIs and reporting versus which need assistance. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.