Migrating off your existing POS. The 90-day window the rep won’t mention.

Two to four weeks for a single location, depending on how clean the data in your current system is. The cutover itself happens overnight — last close on the old system Sunday evening, first open on CannAgent Monday morning. The ramp before that is data audit, hardware swap, and three days of on-floor support during the first week. Multi-location chains stage cutovers one store at a time; we don’t flip ten registers at once. We have run this off Dutchie on our own floors, and the shape is the same coming from POSaBIT, Treez, Flowhub, Cova, BLAZE, Greenbits or BioTrack — what changes is how much of your history the outgoing vendor lets you export, which is the first thing we check.

No. We pull transactions, customers, loyalty points, vendor records, and inventory snapshots out of your current system before the cutover and load them into your new Postgres database. You see your last twelve months of revenue, your loyalty members keep their points, and your vendor history carries over. Anything we can’t migrate cleanly we tell you about up front — we don’t silently drop rows.

METRC continuity is scoped per state during onboarding. The manifest and transfer mapping is built and tested; the live feed connects per store as each operator’s METRC credentials clear — so METRC states (CO, MI, OK, MA, MO, NV, OR, NJ, IL and more) are in build today, not live. Washington runs its own system instead, CCRS, and we build that file natively. BioTrack states — CT, NM, DE — are regulatory coverage right now, not a connected feed. Some states are first-class, others ship as a custom integration on the Enterprise tier, and we tell you which bucket your state lands in before you sign anything.

You keep your data exports and walk — and since setup and onboarding are free, there’s no fee sunk on the way in. We’d rather not work with someone unhappy. The full cross-tier guarantees — compliance built in, no migration fees, named human support, free training, your data stays yours — live at /pricing.

Each location runs on its own Postgres database hosted on Neon, with the application served from Vercel’s edge. The register has an offline cache for the last-known cart state, so an in-flight transaction completes even if the connection blips. A full regional outage on either provider would degrade the back office (analytics, reorder queue) before the register; we’ve held that as the design boundary from the start, because the register is the one surface a sale can’t wait on.