Migrate from Service Autopilot to Pipedrive

Service Autopilot clients map 1:1 to Pipedrive Persons. The client's primary contact name, email, phone, and address fields migrate directly. Client status (Lead vs. Active) maps to Pipedrive's lead/person distinction — active clients land as Persons with associated Organizations; leads without a converted account become Pipedrive Leads.

Service Autopilot commercial accounts represent the business entity — the property management company, HOA, or commercial client. These map to Pipedrive Organizations. The account's primary address, billing address, and associated service locations migrate as address fields on the Organization record.

Service Autopilot allows a client to be associated with multiple commercial accounts (e.g., a property manager with multiple managed properties). Pipedrive Persons can be linked to Organizations via the built-in link model. We create one primary Organization link and surface secondary associations as additional Organization links on the Person record.

Service Autopilot stores each property location separately with its own address, GPS coordinates, and property notes. These locations attach to Commercial Accounts. We migrate the primary service location address onto the Organization record as the main address. Additional locations with distinct addresses become custom address fields on the Organization.

Service Autopilot estimates represent proposed work with line items, pricing, and a status (Draft, Sent, Accepted, Declined). These map to Pipedrive Deals where the estimate total becomes the Deal value, estimate status maps to a custom field, and the associated client/person and commercial account/organization links are preserved. The estimate line items map to Deal Products.

Service Autopilot estimate statuses (Draft, Sent, Sent for Review, Accepted, Declined) map to Pipedrive deal stages. We configure a Pipedrive pipeline with stages matching the estimate lifecycle — typically Won (Accepted), Lost (Declined), and in-progress stages for Draft and Sent. Each stage gets probability values for forecast accuracy.

Service Autopilot jobs are the core operational record — assigned employee, scheduled date and time, service performed, and status (Scheduled, In Progress, Completed, Cancelled). These migrate as Pipedrive Activities: Scheduled jobs become Tasks with due dates and assigned users; completed jobs become completed Tasks with the original completion timestamp preserved. Job notes and photos migrate as Activity notes.

Service Autopilot services and service packages (e.g., Weekly Lawn Care Basic, Monthly Commercial Clean) map to Pipedrive Products with name, description, and default price. When an estimate or job includes specific services, those line items map to Deal Products attached to the Pipedrive Deal record.

Service Autopilot employees with scheduling assignments resolve to Pipedrive users by email match. Unmatched employees are flagged before migration — either invited to Pipedrive first or assigned to a fallback user. Employee roles (Technician, CSR, Manager) become Pipedrive custom fields on the User record for territory and permissions planning.

Service Autopilot invoices are full billing records with line items, payment status, and balance due. Pipedrive has no native billing or invoice object. We migrate invoice total, payment status, and outstanding balance as custom fields on the associated Deal record for historical reference. Actual invoicing and payment collection must be rebuilt in Pipedrive via QuickBooks or Stripe integration.

Service Autopilot custom fields on client records — property type preferences, referral source, preferred contact method — map to Pipedrive custom fields on the Person object. Custom field types (text, picklist, date, checkbox) map to the corresponding Pipedrive field type. Picklist values require value-by-value mapping if the source uses a restricted set.

Commercial account custom fields — contract type, billing terms, property size, access instructions, and client tier classifications — migrate as custom fields on the Pipedrive Organization object. These fields directly support territory segmentation for route planning, account tiering for prioritization workflows, and conditional logic in Pipedrive Automations that trigger onboarding sequences or renewal reminders based on contract expiration dates.