IndicaOnline POS in Massachusetts A Data Migration Guide

image

Moving a dispensary to a brand new POS is a data project sooner than that's a software project. A practical migration preserves the link among products, packages, transactions, and licenses at the same time as leaving unnecessary muddle behind. For an IndicaOnline POS rollout in Massachusetts, agree on scope and attractiveness tests prior to exporting the first document.

Separate operational records from old records

Inventory each and every supply: the previous POS, accounting software program, on line ordering, client statistics, and nation reporting. Decide which statistics have to continue to be searchable, which would be archived, and which the new formula can import. Confirm supported codecs and fields with the implementation staff; do not imagine a finished transaction heritage will transfer.

IndicaOnline's Metrc integration overview describes package deal and happen import. That functionality isn't really kind of like migrating each area from a past POS, so ascertain every one dataset independently.

Build a migration register

    Assign an proprietor to items, bundle balances, clientele, and monetary historical past. Preserve authentic identifiers along any new internal identifiers. Record row counts, extent totals, and the export time for every single dataset. Separate non-compulsory advertising documents from knowledge mandatory for operations.

Use restrained garage for export data. Transfer basically worthwhile knowledge, defend legitimate consent files, and agree https://www.adirs-bookmarks.win/metrc-vs-masscip-a-guide-for-massachusetts-dispensaries on whilst brief copies shall be securely got rid of. Keep required historic information below the shop's retention coverage.

Clean statistics without rewriting the past

Resolve reproduction product names, inconsistent models, and inactive history ahead of import. Keep a cross-reference showing each accredited trade. A spelling correction in the monitor catalog deserve to not silently swap a historic package identifier or mix certain batches.

Reconcile beginning inventory against a actual count number and nation documents on the related cutoff. Distinguish sellable, reserved, held, and in-transit portions. When a change remains unexplained, record and examine it other than altering balances completely to make totals healthy.

Rehearse the cutover

Import a representative pattern first: a widespread object, a multipack, an inactive product, and a report with an exception. Check dates, decimal precision, tax categories, and identifier formatting. Ask crew to retrieve an old checklist and apply its connection to the brand new catalog.

Select a substitute window and freeze nonessential edits. Define how transactions happening after the first export will be captured. Only one equipment may want to be liable for each one dwell regulatory submission for the period of cutover; agree that boundary with equally providers.

Set a clear move or no-move decision

Approve launch purely after rfile counts, balances, and primary workflows pass documented tests. Maintain a rollback plan that identifies the final riskless aspect and the particular person authorised to forestall the migration. Restoring a database does now not undo transactions already standard by means of an exterior method.

After launch, evaluate exceptions day-to-day except sturdy. Compare establishing balances, first sales, and fiscal exports, then retain the migration sign in with the archived resource archives. To speak supported migration selections, be told more approximately IndicaOnline's Massachusetts featuring and bring the sign up on your onboarding assembly.