Migrate from Service Autopilot to Salesforce Sales Cloud

Service Autopilot Client is a unified contact-record that holds personal details, address, billing info, and tags. FlitStack AI splits this into Salesforce Account (for company/billing context) and Contact (for the primary person), with the original client name preserved as Account.Name and first-last name split into Contact.FirstName/LastName.

Service Autopilot distinguishes between Clients (active/billable) and Leads (prospects). Active Clients with no sales history route to Account/Contact; true prospects with no property record route to Salesforce Lead so the sales team can work them through the standard pipeline before converting.

Service Autopilot Properties store service location address, GPS coordinates, measurement data, and photos attached to a specific client. FlitStack AI maps address fields to Account.BillingAddress and stores GPS lat/long as custom fields on the Account. If your Salesforce implementation uses a Location custom object for multi-property clients, we create that object and link it via lookup.

Service Autopilot Job is the core service record — it links a client, property, service type, schedule, assigned employee, status, and invoice. Salesforce Case is the closest equivalent: we preserve the original Job ID as Case.Service_Autopilot_Job_ID__c, map job status to Case.Status, and store the assigned crew as Case.Assigned_Crew__c. Original create dates are preserved as custom datetime fields.

Each employee assigned to a Job in Service Autopilot is a separate assignment record with start time and labor burden. FlitStack AI maps active assignments to Salesforce Tasks with WhoId (Contact) and WhatId (Case) populated; the labor burden is stored as a custom field on the Task since Salesforce does not have a native labor-cost model.

Service Autopilot Estimates contain line items, total amount, and an expiry date. FlitStack AI maps Estimates to Salesforce Opportunities with the estimate total as Opportunity.Amount, the expiry date as a custom field (Estimate_Expires__c), and line items as OpportunityLineItems using a standard Price Book Entry. The original estimate ID is preserved as Source_Estimate_ID__c.

Service Autopilot Invoices are standalone financial records tied to a Job and Client. Salesforce has no native invoice object in Sales Cloud, so FlitStack AI stores invoice totals, balances due, and tax amounts as custom fields on the Account (Invoice_Total__c, Balance_Due__c, Tax_Amount__c) with invoice IDs preserved as Source_Invoice_ID__c for audit continuity.

Service Autopilot Payment records show amount paid, payment method, date, and related invoice. FlitStack AI stores payment totals as a running sum on the Account (Total_Payments__c) and stores individual payment details as a custom Payment_History__c field with a serialized JSON blob so the payment timeline is preserved even without a native object.

Service Autopilot Employees have names, contact info, compensation types (hourly/salary), labor burden rates, and GPS settings. FlitStack AI matches Employees to Salesforce Users by email address. Compensation type and labor burden are stored as custom fields on the User record (Compensation_Type__c, Labor_Burden_Rate__c). If an employee has no Salesforce User, they are flagged before migration so your admin can create the User or assign records to a fallback owner.

Service Autopilot Tags are flat taxonomy labels applied to Clients, Properties, and Jobs. Salesforce has no native tag model; we store the full tag string as a custom multi-select pick-list field (Legacy_Tags__c) on each object where tags exist. Your admin can use these as a reference to build Salesforce Reports or flows that replicate the tag logic.

Service Autopilot Custom Fields per object (text, number, date, pick-list) map directly to Salesforce custom fields using the __c suffix. FlitStack AI creates each field in the target Salesforce org via API, configures field-level security for each profile, and maps values value-by-value for pick-list types using Salesforce's allowed values as the constraint set.

Service Autopilot Notes with body text and timestamps map to Salesforce Notes. File attachments map to Salesforce Files (ContentDocument/ContentVersion), re-uploaded to Salesforce's storage with the original file name and created date preserved as ContentVersion metadata. Files attached to Jobs land on the related Case via ContentDocumentLink.