Manufacturing
Epicor Vantage, Vista and E9 databases: archive, migrate or license?
By SourceX Editorial · Updated
Short answer
Most companies retiring Epicor Vantage, Vista or E9 need all three, in order: a complete archive for retention and audits, a migration of only what the new ERP needs, and a licensing review of the left-behind history before the old server is shut off. An Epicor E9 data archive that was never test-restored may not reopen later.
Key takeaways
- Archive, migrate and license are steps in one plan, not competing choices.
- Migrations usually leave behind closed jobs, labor detail, old quotes and quality history, which is the history most useful to AI developers.
- Settle retention obligations and access needs with finance, quality and counsel before choosing an archive format.
- Know whether the database runs on Progress OpenEdge or SQL Server, because that decides who can restore and read it.
- Restore and verify the archive before the server is decommissioned, never after.
Archive, migrate or license: which is right for old Epicor data?#
Old Epicor data usually needs an archive, a partial migration and a licensing review, in that order, rather than a single choice. The migration carries forward what the new system needs to run the business. The archive preserves everything else for obligations and lookups. The licensing review asks whether that everything else has value outside the company.
The trap is timing. The history most useful to an AI developer, such as closed jobs, labor transactions, old quotes and nonconformance records, is exactly what migrations tend to leave behind. Once the server is decommissioned and the database license lapses, getting that history back can be slow or impossible.
For the CFO, the archive also decides what the company can prove later: transaction trails for auditors, warranty and quality history for customers, and the provenance behind any future license. A verified export kept under company control preserves all three options at once, whatever the final decision on licensing.
What an old Epicor database usually holds#
An old Epicor database usually holds the full operating history of the plant, connected by quote, order, job and part numbers. Module and table names vary by version and by configuration, so build the inventory from your own database and reports rather than a generic list.
| Area | Typical records | Why it matters later |
|---|---|---|
| Quoting | Quote headers and lines, estimated operations and materials, won or lost status | Shows how estimators priced and routed parts |
| Sales orders | Order lines, promise dates, changes and shipments | Links quotes to what customers actually bought |
| Jobs and production | Job headers, operations, material issues and labor transactions | Estimated versus actual hours by operation and resource |
| Purchasing and receiving | Purchase orders, receipts and supplier performance | Supply exceptions and lead time history |
| Quality | Nonconformances, inspection results, discrepant material and corrective actions | Problem-to-disposition reasoning |
| Engineering | Part masters, bills of material, revisions and change history | How products and methods evolved |
| Attachments | Links to drawings, inspection reports and documents on file servers | Often break when the file server moves |
A decision path before you decommission#
The decision path runs from obligations to access to value, and decommissioning comes last. Some steps can overlap, but the server is retired only after every earlier step is closed, because each answer changes what the archive has to keep.
- Step 1, retention: ask finance, quality and counsel which records must be kept and for how long, based on tax rules, customer quality agreements, product liability exposure and certifications such as ISO 9001 or AS9100. If any obligation applies, the archive must stay complete and readable for that period.
- Step 2, access: decide who will need lookups later, such as auditors, warranty staff and customer service. If they need answers within minutes, plan a read-only lookup; if requests are rare, a restorable export may be enough.
- Step 3, migration scope: agree what moves to the new ERP, typically master data, open transactions and a recent slice of history.
- Step 4, licensing review: inventory the left-behind history and run a metadata-only fit check before shutdown. If the history looks licensable, the archive must keep detail tables and their relationships, not just reports.
- Step 5, archive format: choose the format that satisfies steps one, two and four together.
- Step 6, verify and decommission: restore the archive in a test environment, compare row counts and spot-check attachments, then retire the server.
Archive options compared#
Archive options differ in what they keep and how easily the history can be read later. A licensing review needs the underlying detail tables and their relationships, not just reports built on top of them.
| Option | Keeps | Watch for | Fit for a licensing review |
|---|---|---|---|
| Database backup plus server or VM image | Everything, including customizations | Needs the matching database version and skills to restore | Good, if it can be restored and queried |
| Export to SQL Server or another open database | Tables and relationships, readable with standard tools | Character sets, custom fields, date handling | Strong: easiest to inventory and sample |
| Flat files by table, such as CSV or Parquet | Raw data in an open format | Relationships must be documented separately | Good with a data dictionary |
| Read-only reporting archive or archive tool | Lookups for users and auditors | May keep reports rather than detail | Weak unless detail tables are kept too |
| Printed or PDF reports only | Selected documents | Loses structure and links | Poor |
Progress, SQL Server and other technical cautions#
Many older Vantage, Vista and Epicor 9 installations ran on a Progress OpenEdge database, while others ran on Microsoft SQL Server. Confirm which one you have first, because it decides who can restore the database and which tools can read it.
Keep the database backup and an image of the application server together, with license keys, admin credentials held securely and notes on exact versions. A database without its matching environment can be hard to open years later, and the people who knew the system may have moved on. Also check your Epicor license and maintenance terms before relying on a read-only instance, since terms differ by agreement.
- Custom fields and customizations that hold important data outside standard tables.
- Attachments stored as file paths on a server that will also be retired.
- Special characters and character set settings in part descriptions and notes.
- History that was purged or archived out of the live database years ago.
- Several companies or plants in one database, which need separate scoping and signers.
Illustrative: a valve maker retires its Epicor 9 server#
Illustrative: a fictional maker of industrial valves ran Epicor 9 on Progress for many years and is moving to a cloud ERP. The implementation partner plans to migrate part masters, open orders and a recent slice of closed history, nothing more.
The CFO asks for retention guidance first. Quality needs nonconformance and inspection history for customer audits, finance needs transaction history for tax, and customer service wants old order lookups. The IT director exports the full database to SQL Server, keeps the backup and server image offline, copies the attachment folders and documents every custom field.
Before shutdown, the company inventories what the migration left behind: quotes with won or lost status, job labor detail, nonconformances and engineering changes. A metadata-only fit check shows that the quote-to-job history links well. The licensing review continues after the server is retired, because the SQL Server copy was restored, verified and kept under the company's control.
How SourceX fits into an Epicor retirement#
SourceX works alongside the retirement project rather than inside it. The fit check collects metadata only: Epicor version, database platform, modules used, years of history and known restrictions such as customer-owned drawings. No files are shared during the initial assessment.
If the history proceeds through the SourceX five-step transaction of Supply, Rights, Preparation, Approval and Delivery, the data stays in the company's own storage or ships on encrypted drives. SourceX does not host multi-terabyte archives, and the company approves the prepared package before delivery.
Frequently asked questions
Can we license data from an Epicor system we no longer pay maintenance on?
Your business records are generally your own, but how you can access them depends on your software license terms. Check whether you may keep running the old system read-only and whether you can export to an open format. Exporting before maintenance or hosting ends is usually simpler than recovering data later.
Is Epicor Kinetic history handled the same way?
The rights questions are similar, but newer Epicor systems have their own export routes and the history may already sit in a more accessible database. Treat Kinetic as its own inventory, and if you migrated from E9 to Kinetic, check which older history came across and which stayed behind.
How long should we keep the old server image?
Base that decision on retention guidance from finance, quality and counsel, plus any customer quality agreements. One approach is to keep a verified, open-format database export as the long-term copy and hold the server image only until everyone is confident the export is complete.
Which Epicor history is most interesting for AI licensing?
Linked chains tend to stand out: quotes tied to orders, jobs, actual labor and quality outcomes. Engineering change and nonconformance history add written reasoning. Isolated tables, such as a part master on its own, carry less value than the links between them.
Does archiving to the cloud change anything for licensing?
Not in principle. What matters is that the archive is complete, readable and controlled by the company. Check the cloud provider's terms and your security policies, and keep the archive in an account the company owns rather than one held by a former reseller or contractor.
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.