Skip to content

Guide · Switching POS

Change your register. Keep your history, your members, and your consent proofs.

Whether you're leaving a POS by choice, by acquisition, or because the vendor left you, the risk is the same: five years of history, a loyalty list you can't legally use, and a month of double entry. With the ledger in BudAlly, a POS switch is a connector change with two approvers — not a migration project.

Plan a switch with usMigration workspace

WHAT MOVES · WHAT DOESN'T NEED TO

Metrc history since opening
Already in ledger
Loyalty points and members
Never lived in POS
Consent proofs
Carried, or marked unknown
Menu and app
Unchanged; stock source swaps
SKU ↔ item ↔ GL crosswalk
Re-mapped, reviewed
New-customer flags
Carried (no discount reuse)

The seven steps, in order

  1. 1 · LEGACY EXPORT

    Pull everything the old POS will give you.

    Customers, transactions, products, discounts. API where it exists, CSV where it doesn't. Do this before the contract ends.

  2. 2 · MAP

    Crosswalk items and customers.

    Legacy SKU → Metrc item → new POS SKU → GL, auto-accepted at 90% confidence, the rest reviewed. Duplicates merged across stores.

  3. 3 · CONSENT PROOF

    Triage every opt-in.

    With time, source and text → consented. A bare “true” → unknown: kept, not marketed to, re-asked at the next visit. Override disabled.

  4. 4 · LOYALTY RELINK

    Members to new POS ids.

    Auto-relink on email/phone/DOB; a short manual queue for the rest. Points don't move because they never lived in the register.

  5. 5 · DRY RUN

    Reconcile the import to Metrc.

    Store-day sales match, package quantities, open manifests. Run it twice. Fix the map, not the data.

  6. 6 · CUTOVER

    Two approvers, one morning.

    Storefront stock source flips to the new connector; drafts pause during the window; a rollback plan is linked to the approval.

  7. 7 · BENCHMARK

    Four weeks before, four after.

    Tickets/day, AOV, repeat rate, recon match, Metrc reporting lag. If something got worse, you'll know by day 10.

  8. TYPICAL TIMELINE

    Fastest for a single store with API access; longer where the legacy export is email-only. We give you a dated plan once we have seen your export.

Things that go wrong, and what we do about them

  1. 01

    The old vendor won't export.

    Metrc has every receipt and package since you opened; the ledger reconciles legacy gaps against it. You lose some POS-only fields (tags, notes), not the history.

  2. 02

    The loyalty list is a legal liability.

    A migrated “opt-in = true” with no proof isn’t consent under TCPA/CCPA guidance. We import it as unknown and re-ask. It costs you some reach and saves you a complaint.

  3. 03

    First-visit discounts get reused.

    The new-customer flag is carried on every mapped customer so the welcome offer doesn't fire twice.

  4. 04

    Your menu goes dark for a week.

    Not if the storefront reads stock from BudAlly: the connector swaps underneath, the domain and app don't change.

  5. 05

    Nobody can say whether the switch helped.

    The pre/post benchmark runs from the same ledger, with the same definitions, and shows “not significant” when it is.

Planning a switch? Connect the old POS read-only now, so the ledger is there when you flip.

Start free audit

© 2026 BudAlly, Inc. · Not legal advice.