RunMags journal
When Should Publishers Replace Spreadsheets?
A spreadsheet can be a sensible tool for a launch checklist or a small, stable inventory. Replacement becomes worth investigating when keeping several files synchronized consumes time or obscures commitments.
Recognize a control problem
Look for conflicting rate sheets, an unavailable placement sold twice, signed orders missing from production or invoices based on an old price. Another warning sign is a process that only one employee knows how to reconcile. Count those failures instead of assuming that every spreadsheet is a problem.
Keep the useful parts
A small team with a clear owner, few changes and regular reconciliations may not need an immediate migration. Keep analytical worksheets that answer a specific question. Avoid allowing a report export to become a second place where active orders or subscriber terms are edited.
Prepare the migration
Inventory files, fields, formulas and manual rules. Define stable customer, order, issue and product identifiers. Deduplicate records and establish opening balances with finance. Decide which historic data must be searchable and which can remain in a read-only archive. Write down how cancellations and amended placements should appear. If you are moving to RunMags, the data migration guide for legacy systems and spreadsheets walks through the import steps.
Prove the replacement on one cycle
Pilot one issue and compare inventory, material status, invoices and mailing output with agreed control totals. Reopen saved records and ask a colleague to process an exception. Retire editable copies only when owners accept the result; otherwise parallel files can recreate the inconsistency the migration was meant to solve.
A practical worksheet
A migration worksheet can contain file name, record type, owner, unique identifier, update frequency, downstream user and reconciliation method. Add a column for formulas or implicit rules: a salesperson may know that a particular position requires editorial approval even when no spreadsheet field records it. Test those rules using a changed order. Preserve the old file as a dated archive when the replacement is accepted, and communicate which system now owns operational edits. Without that transition, staff may continue repairing exported copies and lose the change at the next import.
Review checklist
- Identify an evidenced loss or repeated reconciliation task.
- Preserve formulas and business rules before importing data.
- Agree the date old operational files become read-only.
