Most card shops do not have one bad spreadsheet. They have a web of useful files that slowly became operational dependencies: a customer-credit sheet, a trade queue, a release preorder tab, an event signup form, and a group chat where employees explain what the files do not show.
Replacing that setup safely means moving workflows, not copying tabs.
Inventory the real system
Start by listing every place employees look during a normal week.
| Current tool | What the shop uses it for | Risk to resolve |
|---|---|---|
| Customer spreadsheet | Names, phone numbers, credit balance | Balance has no ledger history |
| Trade queue tab | Customer, rough offer, status | Items and approvals are not connected |
| Release preorder sheet | Deposits and quantities | Expected and received quantities are mixed |
| Group chat | Payout approval and shift handoff | Decision disappears in conversation |
| Paper event list | Registration and payment notes | No shared capacity or follow-up record |
Ask employees what they check before pricing a trade, issuing store credit, promising a preorder, or closing a drawer. The answer often reveals another hidden source.
Pick a workflow with a clear beginning and end
Do not begin with "move all customer data." Begin with a complete business flow such as:
Customer drops off cards, employee records the lots, pricing is completed, manager approves an exception, customer accepts, cash or store credit is issued once, and the cards move to their next physical step.
That flow identifies the records that must stay connected. A copied trade-queue row does not.
Reconstruct store credit before importing it
A cell containing $184.50 is a balance, not proof.
Before moving store-credit balances, create a reconciliation sheet with:
- customer identity and duplicate resolution;
- old balance as of a named cutoff time;
- unresolved redemptions or additions after that cutoff;
- imported opening balance;
- employee who approved the import;
- source file retained read-only.
Example:
| Customer | Sheet balance at 8/15 9 p.m. | Post-cutoff activity | Opening balance to import |
|---|---|---|---|
| Casey Nguyen | $184.50 | -$35 redemption | $149.50 |
| Luis Ortiz | $72.00 | +$90 accepted trade | $162.00 |
If the shop imports the old balance and later enters the trade again, Luis receives the same $90 twice. Freeze the source, name the cutoff, and reconcile the crossing activity.
Move active trades by physical custody
For every open trade, confirm that the digital record matches what the shop physically holds.
Record:
- customer;
- receiving employee;
- intake date and promised response time;
- lot descriptions, such as "green zip binder, 312 modern singles";
- condition or pricing work completed;
- current offer and approval state;
- exact physical location;
- next employee and due time.
Do not migrate a row marked "pricing" if nobody can find the cards. Do not migrate a box under the counter without creating a record for it.
Split release quantities into separate facts
One cell labeled 48 boxes can mean ordered, confirmed, shipped, received, reserved, or available.
During cutover, separate at least:
- expected from vendor;
- physically received;
- committed to paid or confirmed preorders;
- reserved for events;
- held for another location;
- available for walk-in sale.
This is where a generic spreadsheet import can create a very specific customer problem.
Stop approving money in chat
Group chat can notify a manager, but it should not be the final approval record.
Suppose an employee posts, "Can I do $720 cash on this collection?" and a manager replies with a thumbs-up. The durable record should still contain:
- trade ID;
- estimated resale value;
- normal policy recommendation;
- requested payout;
- approving manager;
- reason for the exception;
- time of approval;
- cash source used after acceptance.
Once the team cuts over, a chat reply without a recorded approval should not release cash.
Use a two-day cutover check
Choose a quiet close for the official cutoff.
Before cutoff
- Resolve obvious duplicate customers.
- Finish or explicitly migrate open trades.
- Count outstanding preorder commitments.
- Export and retain old sources read-only.
- Record control totals for cash, store credit, and active work.
After cutoff
- Compare the new store-credit total with the approved import total.
- Sample at least one customer with additions, redemptions, and a correction.
- Match every migrated trade to physical custody.
- Confirm upcoming release commitments by product.
- Search old chat for decisions made after the freeze.
Set a rule for the old tools
Employees need to know what stops on cutover day.
Example policy:
Beginning Monday at open, customer-credit changes, trade status, payout approvals, release commitments, and shift handoffs must be recorded in the shared operations system. Old sheets remain read-only for 30 days. Chat may alert an employee but does not replace the official record.
Managers have to follow the same rule. A private instruction from an owner will recreate the side channel immediately.
Watch for four migration failures
- Duplicate value: a balance is imported and its source trade is entered again.
- Missing custody: a trade record moves but its physical items do not match.
- Mixed quantity: expected release stock is treated as received or available.
- Split authority: employees keep updating both the old sheet and the new system.
The goal is not fewer spreadsheets. It is one reliable answer when a customer asks about credit, an employee asks whether a trade was paid, or the owner asks how many preorder boxes can actually be handed out.