Start with the jobs your team actually runs.

Begin with a typical call, a scheduled visit, a technician update, and an invoice. Record who does each step and which information changes hands. This reveals the fields, roles, and decisions the system must support.

Clean customer names, addresses, contacts, equipment records, active jobs, and open balances before bringing them across. Agree who signs off on sample imports and what counts as an acceptable mismatch.

Start with working hours, service areas, job types, users, and basic permissions. Advanced automation can wait until everyone understands the daily flow. Avoid changing every company process and every software tool during the same week.

Use representative sample jobs for office staff, dispatch, field workers, and finance. Check actual devices, printing, email delivery, data export, and permission boundaries. Document unresolved issues and choose a safe cutover moment.

Example to try: Before adding a second branch, train one dispatcher and two technicians on a no-cooling call and a return visit, then log missing steps.

• Define one working customer-to-payment path as the first success criterion.
• Clean and sample-import contacts, properties and open work.
• Test user rights, timezone, printer output, and device compatibility.
• Agree who decides whether a pilot is ready to expand.