Switching your store-management system is the single most-feared decision most FFL holders make in a decade — because the A&D book is on the line. It doesn't have to be. This guide breaks the move into four one-week phases. Follow it and you'll be fully live on a new platform in 30 days — with every serialized firearm, 4473, and A&D entry intact and ATF-defensible.
Before You Start: The Three Decisions That Matter Most
Before day one, get clear on three things. Skip these and the rest of the plan collapses.
- The go-live date. Pick a low-volume Monday. Avoid the week before a holiday, tax-refund season, or any inventory event. Tell every employee, every vendor, and your bank.
- The cut-over scope. Are you moving every location at once, or piloting one store first? For 1–3 locations, a single cut-over is faster and safer. For 4+, pilot the smallest store first.
- The owner of the project. Not the IT person. Not the vendor. One person inside your shop — usually the owner or GM — who can make decisions in real time.
The 30-Day Plan, Week by Week
Week 1 · Days 1–7
Discovery & Data Mapping
Goal: know exactly what's moving — and what isn't — before anyone touches a single record.
- Pull a full A&D book export and confirm the column mapping (acquisition date, disposition date, FFL of source/recipient, serial, manufacturer, model, caliber, type).
- Export every open 4473 (any transaction that hasn't completed a NICS clear + pickup yet).
- Pull a full inventory file — every serialized firearm with serial + manufacturer + model + caliber + acquisition date + condition.
- Export non-serialized inventory: ammo, accessories, optics, parts.
- If you run a range: export lane reservation history, membership records, and waiver-on-file status per customer.
- Export the full customer file including any ID + 4473 prior-purchase history.
- Export the last 24 months of sales history.
- List every integration your old system touches: payments, accounting, GunBroker / UsedGuns.com / branded eCommerce, distributors (Lipsey's, RSR, Davidson's), SMS, email, NICS portal.
- Identify three FFL-specific edge cases that always break in demos: a transfer with the recipient's FFL on file, a delayed-NICS pickup, a returned firearm, and a multi-line A&D book entry (e.g. trade-in pair).
- Schedule a 60-minute kickoff call with your new provider's onboarding team and walk them through every export — A&D book first.
Failure mode: assuming the old vendor will hand over a clean A&D book on request. The single biggest switching disaster we see in FFL is a A&D book that doesn't reconcile to floor count. Validate the file yourself in week 1, serial-by-serial, against your floor.
Week 2 · Days 8–14
Configuration & Test Migration
Goal: stand up a sandbox copy of the new system with your real data, and break it before your customers do.
- Load a full test migration into a sandbox environment.
- Configure tax rates per location (and per jurisdiction if you sell online).
- Set up user roles. Don't give everyone admin access "for now" — it never gets fixed.
- Connect payments. Run at least 10 test transactions.
- Reconnect accounting (QuickBooks, etc.) in a test company file.
- Reconnect eCommerce channels and confirm they don't double-sell.
- Walk a full 4473 → NICS check → A&D book disposition entry through the sandbox.
- Run a delayed-NICS pickup (transaction opened day 1, completed day 4) and confirm the A&D book entries are dated correctly.
- Process a customer-to-customer transfer (your shop as the receiving FFL). Confirm both A&D entries.
- Run a return of a serialized firearm and confirm the A&D book records the disposition reversal properly.
- If you have a range: process a lane reservation, walk in, waiver lookup, lane assignment, and checkout.
Pro tip: have your most experienced gun-counter staffer — not your youngest — spend two hours in the sandbox running ordinary transactions. They will find every annoyance long before a customer does.
Week 3 · Days 15–21
Training & Dress Rehearsal
Goal: every person who will touch the system has run a complete shift on it before go-live.
- Run two 90-minute live training sessions per role — gun counter, range/lane, cashier, manager.
- Print a one-page cheat sheet per role and tape it to the back of each register. Include: 4473 start, NICS callback, A&D book entry, transfer, return, end-of-day close.
- Walk through a full 4473 + NICS check + A&D book entry in the new system. Time it. If it's slower than your old workflow, fix it now — counter speed is the difference between making numbers on a busy Saturday and turning customers away.
- Walk through a full ATF-style A&D book audit in the sandbox: pick 25 random serials, trace each from acquisition to current disposition. If any can't be reconciled in under 30 seconds, fix the data before go-live.
- Do a full dress rehearsal: open the store in the sandbox at 9 a.m., run 25 mixed transactions (5 firearm sales with 4473s, 5 ammo/accessory sales, 5 transfers, 10 misc), close the day.
- Identify the one or two staff members who will be on-call during cut-over weekend. Pay them for it.
- Build a fallback plan: if the new system isn't fully usable Monday morning, you must still be able to complete 4473s on paper and back-enter them. Print blank 4473s. Confirm your paper A&D book is at the counter.
- Notify customers with open 4473s, layaways, repairs, or pending transfers about the cut-over window.
Week 4 · Days 22–30
Cut-Over & Go-Live
Goal: close on the old system Friday night, open on the new system Monday morning, and have a quiet week.
- Day 22–25 (Mon–Thu): business as usual on the old system. Do not start "trying out" the new one mid-week — split focus causes mistakes.
- Day 26 (Friday): close out at end-of-day, reconcile, and pull a final full data export. This is your gold copy.
- Day 27 (Saturday): production migration. Vendor loads the final export into live. Spot-check 25 random customers, 100% of serialized firearms (every single one — match serial to floor), and 100% of open 4473s.
- Day 29 (Monday — go-live): open with the owner or GM on the floor, all day. The first 4473 of the morning should be run by the most experienced gun-counter staffer in the building. Confirm the A&D book entry posts correctly before moving to transaction two.
- Day 28 (Sunday): final integrations live — payments, accounting, eCommerce. Run five real (small-dollar) test transactions across each.
- Day 30 (Tuesday): first end-of-day close on the new system reconciled against the bank deposit. If the numbers tie, you're done. If not, fix it before day three.
Failure mode: trying to go live on a payday Friday or the day before a holiday. Don't. The 5% revenue you "lose" by going live on a quiet Monday is a rounding error compared to the chaos of a botched cut-over.
The First 90 Days After Go-Live
The plan doesn't stop at day 30. Most of the long-term value of a new platform shows up in the next 60 days, but only if you actually use it.
- Week 5–6: turn on every report your owner looks at weekly. Run a mock ATF A&D book audit on yourself by week 6 — it's much cheaper than the real one.
- Week 7–8: activate eCommerce. FFLs typically see a 15–30% lift in online revenue within the first quarter of a Bravo deployment once GunBroker, UsedGuns.com, and your branded site sync are live.
- Week 9–10: retire the old system. Cancel the contract.
- Week 11–12: first quarterly review with your vendor's customer-success team. Schedule your annual ATF audit-readiness review.
The Six Mistakes Almost Every Switching Project Makes
- Trying to migrate every line of historical data. Active records + 12 months of history is plenty. Archive the rest in a read-only export.
- Letting the vendor do the data validation. They don't know your business. You do. Spend the four hours.
- Training only the new hires. Your most senior staff have the most muscle memory to unlearn — they need the most training, not the least.
- Forgetting the printer / scale / scanner / signature pad. Hardware compatibility eats more go-live weekends than software bugs do. Confirm every peripheral in week 2.
- Underestimating the A&D book conversion. The A&D book is the riskiest piece of the migration. Treat it like its own project inside the project — separate validation pass, separate sign-off, separate reconciliation against floor count.
- Going dark on customers. One short email before, one during, one after. That's all it takes.