Migrate from Service Autopilot to Nutshell

Service Autopilot has no documented public REST API for programmatic data extraction

Unlike most CRMs that FlitStack migrates, Service Autopilot does not expose a documented REST API for external data extraction. The only egress path is the admin-gated XLS export (Settings > Export > Export Clients, Export Jobs, etc.), which requires User Roles and Rights to be configured to allow export before the migration user can access it. The export generates asynchronously and appears on the My Day Page under Recent Exports when complete. FlitStack parses the XLS file, extracts all records with their linked properties, jobs, and custom field values, and maps them to Nutshell's API-compatible structure before loading. This export-first extraction path adds planning steps that API-first migrations do not require.

Nutshell has no native job costing, invoice generation, or payment tracking objects

Service Autopilot's core value for field-service teams is its job costing model: employee labor burden rates, material costs, profit margins, invoice generation, and payment recording all live inside the Job record. Nutshell is a sales CRM — Deals have a name, amount, stage, and expected close date, but no native fields for cost accounting, invoice PDFs, or payment history. FlitStack handles this by storing job costing totals (Labor_Cost__c, Material_Cost__c, Total_Job_Cost__c, Invoice_Total__c, Invoice_Status__c) as custom currency and pick-list fields on the Deal. Invoice PDFs are preserved as file attachments. Teams that rely heavily on job costing reports should plan to export Service Autopilot job costing data and maintain it in a spreadsheet or dedicated accounting tool post-migration.

Service Autopilot automations and sequences have no equivalent trigger model in Nutshell

Service Autopilot's automation engine is built around field-service events: job completion, GPS arrival at a property, client check-in, invoice payment, and employee clock-in all serve as automation triggers. Nutshell's Personal Email Sequences are scoped exclusively to sales pipeline events — a lead entering a stage, a deal stage changing, or a contact replying to an email. These are fundamentally different automation models, and there is no import or translation path between them. FlitStack exports the Service Autopilot automation definitions as a structured document listing each sequence name, trigger type, conditions, and action steps. The Nutshell admin uses this document to rebuild equivalent sequences using Nutshell's trigger-based sequence builder. There is no automation parity guarantee — some Service Autopilot triggers have no Nutshell equivalent and must be handled manually or via a third-party integration.

Nutshell contact-tier billing means large client databases may require a plan upgrade to accommodate migrated records

Nutshell uses a contact-tier pricing model: the Foundation plan starts at 100 contacts and scales in tiers up to 900,000+ contacts on Enterprise. Service Autopilot does not impose a contact cap but tiers its pricing by mobile-user and business-user counts. Teams migrating from Service Autopilot with large client databases (5,000+ contacts) will need to verify that their chosen Nutshell plan accommodates the migrated contact count. FlitStack identifies the total unique client and lead count during the sample migration phase so the team can confirm plan fit before committing to the full migration. Upgrading to a higher Nutshell contact tier incurs an ongoing monthly cost that should be factored into the total cost of migration.

Service Autopilot's XLS export does not include employee labor burden rates by default — they require a separate report extraction

Employee labor burden rates (the hourly cost per employee used in Service Autopilot's job costing calculations) are stored on the Employee record in the Payroll/Job Costing tab. The standard XLS export does not include this data — it requires running the Run Reports for Job Costing report or extracting Employee data separately. FlitStack's sample migration identifies whether labor burden data is present in the export; if not, we flag it and advise the admin to provide the Employee export so the rates can be mapped to custom fields on the relevant Company records. Missing labor burden data means historical job cost profitability cannot be calculated in Nutshell.