Prophet 21 cloud migration: what to do with your historical order data

What happens to order history in a Prophet 21 cloud move?#

What happens to order history in a Prophet 21 cloud move depends on which move you are making. Moving your existing P21 database to an Epicor-hosted or SaaS environment generally keeps history with the database, while leaving P21 for a different cloud ERP usually brings across masters and open transactions and little else.

Even in a like-for-like move, access changes. On premises, your team or partner may have queried the database directly, run custom reports and linked documents on local file shares. In a hosted environment, direct database access, custom objects and file paths may work differently, so confirm with Epicor or your partner what will be available after go-live.

Treat the migration as the moment to decide what history you keep, where it lives and who can reach it once the legacy server is shut down. That decision is much harder to make after the hardware has been wiped.

Migrate, archive or export: comparing the options#

Migrating, archiving and exporting are not exclusive, and most IT teams combine them. The table compares the options for closed orders and the history around them.

Whichever mix you choose, verify it. Pick a sample of old orders and confirm that each one can be found, with its lines, notes, attachments and invoice, in the place you expect after cutover. A verification log signed by the IT director and the controller is a simple, durable record.

What to keep before cutover#

Before cutover, keep every table that describes a business event, not just the ones the new system needs to run. Compare this list with your partner's conversion scope to find the gaps.

Include canceled and lost business. Canceled lines, expired quotes and returns are often filtered out of conversions as clutter, yet they show demand that went unmet and problems that were fixed, which makes them some of the most informative records a distributor holds.

• 1Order headers and lines, including canceled lines and backorders.
• 2Quotes and their conversion to orders.
• 3Invoices, credit memos and return authorizations with reason codes.
• 4Purchase orders, receipts and vendor returns.
• 5Inventory transactions, adjustments and cycle count results.
• 6Customer and ship-to masters with historical contacts and terms.
• 7Item master with supersessions, customer part number cross-references and discontinued items.
• 8Price pages, contracts and their effective dates.
• 9Notes and activities attached to orders, customers and items.
• 10Document attachments such as scanned purchase orders, packing lists and proofs of delivery.
• 11User-defined fields, custom tables and audit columns showing who changed what.

Where history slips through: notes, attachments and customizations#

History slips through in the places a conversion template does not reach: free-text notes, document links and customizations. Each needs a deliberate decision.

Notes often live in separate tables keyed to orders, customers or items, and conversions frequently skip them. Attachments are often stored as file paths that point to a server share, so the database row survives while the document becomes unreachable. Export the files with a manifest that maps each document to its order or customer ID.

Customizations are the third risk. User-defined fields, business rules and reports built up over many years encode how the business actually ran. Document what each custom field meant and when it was introduced, or the exported values will mean nothing to anyone who reads them later.

Reports deserve the same treatment. Export the definitions of key custom reports, not only their output, so the logic behind familiar numbers survives the move.

Questions to settle with Epicor or your partner#

Settling a short list of questions in writing before cutover avoids most surprises. The answers belong in the migration plan, not in someone's memory, and they should name who is responsible for each export.

Illustrative: an MRO distributor keeps its order history in company storage#

Illustrative: Northgate Industrial Supply, a fictional MRO distributor, has run Prophet 21 on its own servers for many years and is moving to Epicor's cloud offering. The conversion plan covers the live database, but the IT director notices that order attachments point to a file share scheduled for retirement.

Before cutover, the team takes a full backup of the legacy database, exports the attachment folders with a manifest keyed by order number and documents every user-defined field. It keeps a read-only copy in company-owned encrypted storage, separate from the hosted environment, and records who can access it.

Later, the CEO asks whether the company's order and return history could interest AI developers. Because the archive is intact and documented, the IT director can answer a metadata-only fit check quickly: systems, years covered, record families and known restrictions.

Why the archive matters later, and how SourceX fits#

The archive matters later because order lines, returns, substitutions and notes describe how a distributor actually serves customers, the kind of linked operational record AI developers look for. A complete archive also supports audits, warranty disputes and a future sale of the business.

SourceX never hosts multi-terabyte datasets; large archives stay in your own storage or ship on encrypted drives. Under the SourceX five-step transaction, nothing moves until your company has reviewed the scope in the Rights and Preparation steps and approved the release.

The SourceX Evidence Packet then documents provenance for the exported tables, including source system and export date, alongside the rights relied on, the permitted use, the privacy treatment and your release authorization.