Migrating Hotspot Records and Existing Customer Access

WayaDesk / Installation and migration

Before migrating a hotspot, identify which records describe unused vouchers, issued access, persistent customers and collected payments. Treating everything as a single customer list can lose the meaning of important records.

Preserve the original export

Keep an unchanged copy and inspect representative entries. Map identifiers, package rules and expiry values into the supported import workflow. Resolve duplicate or incomplete records before moving the full dataset rather than asking the new system to guess their meaning.

Check access and money separately

Imported entitlement is not a new sale. Existing issued access and unissued voucher stock also have different purposes. Compare the resulting records with the original business evidence before allowing staff to resume normal sales.

• Test a small sample with different service states.
• Check duration and supported limits on the actual access path.
• Record which system controls each part of the transition.

Coordinate the cutover

Choose a clear point at which the new installation takes responsibility for the selected customers. Preserve a way to reconcile payments received during the transition. Avoid running competing controllers against the same access records without a deliberate design.

Make rollback practical

Define the conditions that would stop the migration and the records required to return safely. A successful import count does not prove that customers can connect or that unused voucher inventory remains correct. Complete both the record comparison and the live service checks before expanding.