Migrate from Service Autopilot to HighLevel

Service Autopilot Clients map directly to HighLevel Contacts. Name, email, phone, address, and all custom client fields migrate as contact fields or custom fields. Original create date preserved as Created_From_Service_Autopilot__c for reporting continuity. Owner assignment resolved by email match to HighLevel users.

Service Autopilot Properties (service-location records with address, GPS coordinates, measurements, photos) map to HighLevel Companies. Property-specific fields — lot size, square footage, service frequency notes, and GPS coordinates — migrate as custom fields on the HighLevel Company record since HighLevel Companies use a standard address model without field-service measurement fields.

Service Autopilot's client-to-property link (one client can have multiple properties) maps to HighLevel's Contact-Company association. If a client has multiple properties, all associated Company records are created and linked to the primary Contact — a one-to-many relationship that HighLevel handles natively.

Service Autopilot Jobs map to HighLevel Opportunities within a configured Pipeline. Job status (Scheduled, In Progress, Completed, Cancelled) maps to pipeline stage values. Each distinct job type in Service Autopilot can optionally map to a separate HighLevel pipeline — your admin decides whether to consolidate into one pipeline or preserve multiple job categories as separate pipelines with their own stages.

Service Autopilot assigns Jobs to Employees or Teams. This assignment migrates as a custom field (Assigned_Employee__c) on the HighLevel Opportunity and/or creates linked Tasks assigned to the matched HighLevel user. Routing order (stop sequence) from Service Autopilot's dispatch board migrates as a custom integer field for reference.

Service Autopilot Estimates — proposals with line items and pricing — map to HighLevel Opportunities with status set to the estimate's state (Draft, Sent, Approved). Line items from the estimate migrate as custom fields or a linked custom object, since HighLevel Opportunities do not have native line-item tables the way Service Autopilot Estimates do.

Service Autopilot Invoices (with payment status, balance, and line items) migrate as Opportunity custom fields capturing invoice number, amount, payment status, and balance due. If you have high invoice volume, we recommend a separate Invoice custom object in HighLevel to avoid cluttering Opportunity records — this is configured before migration and adds custom-object setup to the scope.

Service Autopilot Employees map to HighLevel Users for team management. Employee details (name, email, role, phone) migrate as user profile information. Payroll-related fields like Hourly Rate and Labor Burden from Service Autopilot's Job Costing tab do not have a native HighLevel equivalent — we preserve them in a custom field on the user record as reference data for your admin.

Service Autopilot custom fields on any object migrate as custom fields on the corresponding HighLevel object. Field types map to HighLevel equivalents: text to Text, number to Number, date to Date, dropdown to Dropdown (with value-by-value mapping if source uses specific pick-list values). All custom field definitions are exported from Service Autopilot during the pre-migration audit and created in HighLevel before data migration runs.

Service Autopilot notes on Clients, Properties, and Jobs migrate as HighLevel Notes attached to the corresponding Contact, Company, or Opportunity record. File attachments (photos, documents) are downloaded and re-uploaded to HighLevel's file storage, preserving the original filename and linking to the parent record.

Service Autopilot Automations and Sequences do not have a migratable equivalent in HighLevel. Each platform uses a distinct automation logic engine, and export/import between them is not technically possible. FlitStack exports your Service Autopilot automation definitions as a structured PDF reference document showing triggers, conditions, and action sequences — your HighLevel admin uses this to rebuild workflows in HighLevel's Workflow builder.

Service Autopilot payment records (credit card charges, payment history linked to invoices) migrate as custom fields on the associated Opportunity capturing payment date, amount, and payment method. The actual payment processor connection (Service Autopilot's integrated payments) must be replaced with a HighLevel-supported payment integration — Stripe, Square, or another provider — configured separately post-migration.