Print MIS migration: what job history to keep when you switch

What job history should you keep when you switch print MIS?#

When you switch print MIS, keep three buckets of job history: migrate what the new system needs to run work, archive closed jobs and estimates in a readable form, and assess the estimate-to-actual history for its value before anything is deleted. Migration projects usually focus on the first bucket, and the other two are easy to lose.

Commercial printers switch for familiar reasons: an on-premises system nearing the end of support, a merger that leaves two systems running, or a move from PrintSmith or ePace to PrintIQ or another cloud platform. In each case the plan is built around open work, and closed history is treated as an afterthought.

Closed history is where the business knowledge sits. Years of estimates against actuals show how your presses, bindery and finishing really perform, which jobs make money and how customers change jobs after approval.

Migrate, archive or assess: the three buckets#

The three buckets sort every record type by what the business needs from it after cutover. The assess bucket is the easiest to lose by default, because no one needs it to run tomorrow's jobs.

How to get closed history out of the old MIS#

Closed history comes out of an old MIS by one of three routes: built-in reports and exports, a copy of the underlying database, or an export performed by the vendor. The right route depends on whether the system is on-premises or hosted and on what your contract says.

Whichever route you use, keep job numbers, estimate numbers and customer IDs unchanged so records can be rejoined. A closed job without its estimate number tells you what ran, but not what you expected when you priced it.

Verify before you switch anything off. Pick a handful of closed jobs, including a reorder, a job with author's alterations and a job that lost money, and confirm the archive shows the estimate, the revisions, the actuals and the notes for each.

• 1Built-in reports: export job, estimate and cost center reports to CSV, year by year. They are easy to run, but reports often summarize and drop notes and line detail.
• 2Database copy: for on-premises systems, a backup or read-only copy keeps every table and link. You need someone who can query it later, or a reporting view built before the old system is shut down.
• 3Vendor export: hosted systems usually depend on the vendor. Ask in writing which tables and attachments are included, the file format, any fee and how long you keep access after notice.

What to check in both contracts before you give notice#

Check the old MIS agreement and the new vendor's terms before giving notice, because both affect what you can do with your own job history. The old agreement governs export help and access after termination; the new one governs how migrated data may be used by the vendor and how you could leave later.

Do this before signing the new agreement, while terms can still be negotiated. A clause on aggregated data or AI training is far easier to change before signature than after.

Illustrative: a commercial printer archives before switching#

Illustrative: Bramblecote Printing is a fictional commercial printer running offset, digital and wide-format work with an in-house bindery. It had run an on-premises MIS for many years and chose a cloud MIS after merging with a smaller digital shop that used a different system.

The new vendor's migration covered customers, price rules, stock and open jobs. The COO added a second workstream: a read-only copy of both old databases, a reporting view joining estimates to jobs and cost center actuals, and an export of job and press notes. Customer artwork stayed on the prepress file server under the existing retention practice.

After cutover, the archive answered reorder and dispute questions, and the estimate-to-actual view became the reference for setting up the new system's cost centers. The COO then listed the assess bucket in the company's data inventory to judge later whether it could support a license.

Why estimate-to-actual history outlives the migration#

Estimate-to-actual history outlives the migration because it records how experienced estimators priced work and how the plant actually performed. That pairing is what AI estimating tools need to learn from, whether you build one, buy one or license the records to a developer.

The history is most useful when each job keeps its specification, the estimate and its revisions, actual hours and materials by cost center, and any author's alterations. Notes explaining why a run took longer, such as a stock substitution, a color match or a bindery problem, add context no field captures.

Some records stay out of any outside use: customer artwork and files, customer names and pricing agreed under confidentiality terms. What remains describes the printer's own operations.

How SourceX approaches print MIS history#

SourceX approaches print MIS history as a system-retirement case: preserve first, then assess. The SourceX five-step transaction starts at Supply with a metadata-only fit check covering systems, years of accessible history and record families, and no files are shared at that stage.

If the history qualifies, Rights checks customer terms and both MIS contracts, Preparation removes customer identities and personal details, and the printer approves every file before Delivery. The records are licensed, not sold outright, and the printer keeps ownership.