Planning a move from desktop to cloud
Define your data, workflows and acceptance checks before moving your shop to another edition.
Name the reason for moving
An additional branch, individual device tracking or an owner’s remote workflow may justify evaluating another edition. A growing repair count alone does not prove that you need a different product. Define the missing capability and demonstrate it in the proposed destination.
List what must move
List products, quantities, customers, open repairs and historical sales separately. Snap provides an export workflow, but exporting does not establish that every record can be imported. Agree supported fields, missing information and historical access with the team before making a commitment.
Rehearse using an authorised copy
Use a controlled copy of the data and protect customer information. Compare counts and totals before and after the trial import. Investigate differences in taxes, rounding, stock quantities and open job balances. Do not call the migration complete just because the upload succeeded.
Plan the day you change systems
Agree who performs the final backup, when data entry stops, who verifies the new system and what happens if acceptance fails. Keep a rollback plan and the original backup. Train staff on the tasks they perform rather than only showing an overview dashboard.
Confirm the commercial scope
Ask which migration work is included, who handles exceptions and what ongoing support covers. Confirm the new subscription and renewal terms. Retain the agreed scope and acceptance results so both your team and support have the same understanding.
Next: compare editions and pricing, or find an answer in the help centre.