{"@context":"https://schema.org","@type":"BreadcrumbList","@id":"https://cannagent.ai/migrate#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://cannagent.ai/"},{"@type":"ListItem","position":2,"name":"Migrate","item":"https://cannagent.ai/migrate"}]}
Migration

What changes when you leave your current POS.

The cutover sequence does not change by vendor — two to four weeks for a single location, overnight switch, three days of on-floor support. What changes is how much of your history the system you’re leaving will actually hand back, and that is the first thing we check.

Below is what operators tell us they leave each system over. It is not a list of connectors we have built — we have run this migration off Dutchie on our own floors, and everything else is scoped against your export before anyone signs anything.

Systems we have mapped the cutover for

DutchieTreezFlowhubCovaBLAZEMeadowKorona POSPOSaBITBioTrackGreenbitsSpringBigiHeartJane

Running something else? The sequence is the same. What differs is what your current vendor will hand back, and we check that first — before you commit to anything.

We have run this migration off Dutchie on our own floors. That walkthrough is written up in full.

Your system isn’t on this list?

The sequence is the same. Tell us what you’re running and what your contract says about getting your data out, and we’ll tell you what a cutover actually looks like before you commit to anything.