Cutover
A typical 4-week migration plan
What CannAgent onboarding looks like — 12 milestones across a typical 4 weeks, in order. Your dates are set in a written scope. No vendor jargon; no ‘your dedicated success manager will be in touch’ — just the work, in order.
Leaving a specific system? What changes coming from each POS — the sequence below does not change by vendor; what you can export does.
Why this is published
Most POS vendors hide the cutover plan until you’ve signed. We publish ours because the operator deciding whether to switch deserves to know what week 3 looks like. The 12 milestones below are the same checklist we work from once you sign — there is no second, private version.
Week 1 · Data + access
We pull your existing POS data, verify the row counts, and provision admin access for you + your lead staff. No surprises on day one of week two.
Data export requested from prior POS
Email the vendor for a CSV of products + customers + loyalty + transaction history.
Data export received + verified
Spot-check the row counts + confirm no PII leaked through unredacted columns.
Operator-team + lead staff have admin access
Admin access set up for you and your lead staff, with credentials handed over securely.
Week 2 · Config + dry run
Catalog imported, tax rules locked in, register hardware tested end-to-end. Sandbox dry-run with YOUR data — not a generic demo.
Catalog imported + tax rules verified
Per-state excise + sales/use + local-option rates locked in; cross-check against last week’s receipts.
Register hardware setup + tested
iPad + receipt printer + cash drawer + scanner on the LAN; one full cart cycle clears end-to-end.
Sandbox dry-run with operator-data
Operator’s actual catalog in a sandbox; lead staff rings 10 sample transactions; variance reviewed.
Week 3 · Training + parallel
Two distinct training paths: a warm 30-minute CannAgent-specific brief for existing staff who already know POS work, and a cold full-curriculum session for any new hires joining during the cutover window. Then a parallel-shadow day where CannAgent runs alongside the old POS, and a compliance dry-run for recall + sale-to-minor + surveillance.
Existing-staff CannAgent brief — warm path
~30-minute per-shift walk-through for staff who already know POS work. Covers only what is different here — navigation, the manager-PIN override flow, the compliance gates, the age-check flow. Skip the ‘what’s a register’ basics — they know.
New-hire full training — cold path (if hiring during cutover)
Multi-hour curriculum for staff hired during or just before the cutover window. Full budtender training: register basics + industry/heroes/medical-discount verification on house policy + sale-to-minor blocks + surveillance discipline + customer-script. Skip if no new hires during cutover.
Parallel-run day done (shadow mode)
One full open-to-close day on CannAgent in shadow alongside the old POS; reconciliation matches.
Compliance dry-run (audit log + recall + ID-scan)
Synthetic recall walk-through, sale-to-minor block test, surveillance-retention probe — all pass.
Week 4 · Cutover
End-of-day Monday cutover so Tuesday opens clean. Day-7 standup confirms the dust has settled. We’re still on daily check-ins for the full first week.
Cutover at end-of-day Monday
Final reconciliation on the old POS; new POS becomes the source-of-truth Tuesday open.
Tuesday open — no in-flight transactions
First customer at 9 a.m. clears on the new system; no fallback to the old register needed.
Day-7 post-cutover standup
Daily 10-min standup for 7 days complete; weekly cadence kicks in for next 3 weeks.
Read deeper
- /guides/pos-migration-playbook — the long-form deep-dive these 12 milestones come out of. Migration timing, the ‘why end-of-day Monday’ decision, what to tell staff during the parallel-shadow day.
- /pricing — what a cutover costs and how pricing scales past one location.
Ready to talk through your cutover?
The demo call is where we map your specific data + staff roster + cutover-Tuesday window into the 12-milestone plan above. Fixed scope at the end of that call.