Switching print shop software: a migration checklist before you cancel

Separate contacts, history and live work

Create three inventories. Contacts contain customers and their contact details. Historical records contain prior quotes, revisions, approvals, files, deliveries and financial evidence. Live work contains the orders that still require an operational decision. Moving one category does not prove the other two moved correctly.

For every export, record the source system, export date, responsible person and intended destination. Retain an untouched copy. Do not assume a report CSV includes binary artwork, all revisions or attachment access; inspect the actual files and ask the provider what the export contains.

Printavo’s guide about moving into Printavo distinguishes customer/product CSV imports from quotes/orders, for which it describes an API-based option. This concerns imports into Printavo; it does not establish what your account can export when leaving. [1]

Prove the mapping with a small batch first

Select a few varied, authorized records: a simple order, a revised order, multiple garment lines, a cancelled job and a partial delivery. Compare the source and destination field by field before importing a larger batch. Keep the original identifiers as references even if the destination creates new IDs.

For files, compare a checksum when one is available and also inspect the file’s role. Matching bytes prove that a file has not changed during transfer; they do not prove that it was the approved version or suitable for production. A missing relationship between a file and a revision still needs resolution.

Write exceptions into an issue log. Examples include missing originals, ambiguous customers, unavailable approval timestamps and different tax or discount representations. Decide whether to correct, archive with an explicit limitation or leave that record in the old system. Do not silently manufacture missing evidence.

YoPrint documents a CSV option for bulk customer import. That is evidence about customer records, not a promise that the same file transfers all historical orders, approvals or production originals. [2]

Give open orders one operational owner during cutover

Choose a cutover window and list exactly which live orders move. For each, record the current approved revision, materials on hand, production status and quantities still to deliver. Identify which system remains authoritative until each check is complete.

Avoid two independently editable “current” records. During a rehearsal, the second system may be a read-only copy. When an order truly switches, tell the involved staff where future changes must be recorded and retire obsolete paper tickets. If the customer specification changes, handle it as a revision rather than disguising it as a migration repair.

Test the way out before closing the old account

Ask the source provider which exports remain accessible after cancellation, for how long, and under which plan or support arrangement. Get the answer for your actual account rather than inferring it from a generic marketing page. This guide does not state a universal retention period.

Keep a verified fallback copy and an agreed recovery procedure. Test whether someone other than the exporter can find a sample customer, reconstruct an order and retrieve its original file. A download that nobody has opened is not yet a usable fallback. Delay cancellation if unresolved live orders still depend on inaccessible records.

What PrintLatch can import today

PrintLatch’s CSV importer maps supported columns into new drafts. Its portable JSON archive can retain read-only history with originals, validate referenced files and checksums, and deduplicate repeated imports. The current portable bundle limit is 100 orders and 20 MB of original files; archived approvals do not create active production permission.

These are different jobs. CSV draft import is not a promise to reproduce historical approval, payment and file relationships. Portable PrintLatch archives are not a direct parser for Printavo or YoPrint exports. A source-specific conversion needs an authorized export sample, mapping and validation before anyone can call it a migration path.

Use the local migration tool to inspect the supported format and preflight behavior. If your required record cannot be represented without losing meaning, stop at the preview and resolve the mapping; do not treat a successful HTTP response as business acceptance.

A go / no-go checklist for the owner

Approve the switch only when the people who quote, approve, produce and hand over goods can carry out their work in the agreed destination. Keep subscription setup, payment-provider setup and data acceptance as separate checks.

• Representative records match their source quantities and amounts.
• Files are present and associated with the correct versions.
• Open jobs have one clearly assigned source of truth.
• Staff know how to record new changes and partial deliveries.
• Historical approvals remain historical evidence.
• Unresolved exceptions and the rollback decision are written down.
• The old account is cancelled only after access and fallback are confirmed.