The key idea

A publisher migration moves several different kinds of records: product identities, historical demand, current physical stock, open commitments and financial balances. Each needs its own meaning and cutoff. Importing all of them as generic transactions can duplicate sales, reserve old orders or create stock that was never physically verified.

This is an original operational explainer. Its examples and decision rules are illustrations, not measured customer results or universal service commitments.

Choose a consistent transition point

Agree when the old process stops being the source of new operational events and when the new one begins. Record how transactions during the transition are handled. Preserve source exports and row counts. Opening stock must state whether it includes reservations or damaged units. Open orders should be identified separately from completed sales history. Financial credit needs confirmation through the responsible finance process, not a number copied from an unverified spreadsheet.

Reconcile before enabling automation

Check totals by edition and market, sample individual records and resolve ambiguous identifiers. A migration can pass a row count check while still mapping demand to the wrong binding. Confirm that repeating an import does not duplicate records. Keep a controlled correction process and an audit trail. Automatic replenishment should remain off until the data and its coverage are understood, because a migration error can otherwise become a real production expense.

Worked example · illustrative assumptions

Suppose the old system reports 100 physical copies, of which 20 are already committed to open orders. If the new system imports 80 as available stock and then subtracts the same 20 reservations again, it shows only 60 available. If it imports 100 and ignores the open orders, it shows too many. The correct result depends on preserving the original definitions and reconciling the commitments explicitly.

Put it into practice

  • Separate catalog, history, open orders, stock and funds imports.
  • Agree a transition cutoff and record late arriving events.
  • Reconcile definitions and sample mappings before enabling paid automation.

Watch out for

Do not delete migration evidence once the dashboard looks plausible. Later discrepancies often require the original export, import reference and transformation rules to explain what happened.

Is a phased migration acceptable?

Yes. A selected catalog and market can reduce risk if the boundaries are clear. Ensure the same orders and stock are not being managed independently by both systems.

AI assisted editorial content with original planning examples. Source links support the stated source notes; operational suggestions are guidance rather than guarantees. Provider rules and product coverage can change. Editorial approach · BooksAhead.ai connection status.