Migrate your Service Autopilot data

Clients are the primary customer records in Service Autopilot, accessible via CRM > Clients. They support export via the Export Clients action, with related Properties and Tags linked at the client level. We migrate Clients as the top-level record, pulling all standard fields and related properties.

Leads (also called Prospects) are tracked separately from Clients and have their own list in the CRM module. The comparison chart confirms 'Prospect & Leads Tracking' is included at all paid tiers. We map Leads into the destination's equivalent Lead or Contact object, preserving lead status where applicable.

Properties are associated with Clients and store address, GPS coordinates, measurements, and photos. The user guide shows Smart Maps integration with customizable GPS coordinates. We extract property records and map them to the destination's location or site object, though coordinate precision and photo attachments require case-by-case handling.

Jobs are the work orders scheduled via the Dispatch Board. They include assigned employees, services, status, and scheduling windows. Jobs can be exported and imported via templates. We migrate active and historical jobs as work order records with their assignment and status history intact.

Employees (Team members) are managed under Team > Employees with compensation types (Hourly vs. Salary) and labor burden rates for job costing. GPS tracking links to employee records. We migrate employee profiles, compensation settings, and role assignments.

Invoices are generated from jobs and support bulk export from the Invoices screen. The platform supports credit card charging per invoice. We migrate open and closed invoices, preserving line items, totals, and payment status.

Payments are tracked separately and can be exported from the Payments list. Autopay settings on Client Portal are linked to payment records. We migrate payment history including method, amount, date, and associated invoice reference.

Estimates are a type of non-billable job that can be scheduled with or without a Client/Lead. The FAQ confirms estimates are a distinct scheduling type. We map estimates to the destination's Quote or Estimate object, preserving line items and status.

Automations are composed of Sequences with triggers, conditions, and events (email, task, etc.). They are stored as workflow configurations, not as exportable records. Service Autopilot does not provide a bulk export for automation logic. We document the automation inventory during scoping and recommend manual rebuilding at the destination.

Tags can be added to accounts and clients. The Accounts user guide confirms Add/Remove Tags functionality. Tags are scalar label values rather than structured data. We map tags as string arrays on the associated record, noting that destination tag taxonomies may differ.

Custom Fields are created under Settings > Custom Fields and attached to various objects. The platform supports custom field creation per object type. We migrate custom field values as key-value pairs, mapping them to destination custom fields that may need to be created first.

Schedules are imported via a dedicated Import Type in the Import Data tool. Scheduling FAQs confirm that schedules can be imported and exported. We map schedule records to the destination's calendar or scheduling object, handling date/time format normalization.

Job Costing reports depend on employee compensation, service/product setup, and job close-out data. The user guide explicitly warns that accurate job costing requires correct setup upstream. We migrate the underlying data (jobs, employees, services) that feeds reporting, but the reports themselves are not exportable and must be regenerated at the destination.

Export permissions and feature access are gated by User Roles and Rights. The platform confirms that the Export option may not appear if rights are not enabled. We map user roles to the destination's permission model, noting that feature-gated capabilities may differ between platforms.