Migrate from Ascora to Pipedrive

Ascora customers hold both contact details and business entity information. FlitStack AI splits these: business name and address migrate to Pipedrive Organization; individual contact name, email, and phone migrate to Pipedrive Person linked to that Organization. Where a customer record has no business name, it lands as a standalone Person.

Ascora site contacts (on-site liaisons, property managers, facility coordinators) map directly to Pipedrive People. They are linked to the Organization representing the site address. Multiple contacts per Organization are supported natively in Pipedrive, and each contact retains their role designation as a custom field.

Ascora's Site records hold the physical address, property type, and site-specific notes. Pipedrive Organizations store address fields natively. Site-specific notes migrate as a custom field (Site_Notes__c) on the Organization. Each unique site address creates one Organization record, preserving all address components including city, state, and postal code in their corresponding Pipedrive fields.

Ascora equipment records (make, model, serial number, install date, service history) have no Pipedrive equivalent. We store equipment details as custom fields on the Organization linked to the site where the equipment is installed. Equipment lists with multiple items per site are serialized into a custom text field or JSON-structured custom field.

Ascora jobs are the core object — they hold the customer link, site link, job type, status, priority, assigned technician, and line items. Each job maps to one Pipedrive Deal. Job status (Quoted, Scheduled, In Progress, Completed, Invoiced) maps to Pipedrive stage values within the migration's designated pipeline. Job ID is preserved as Source_Job_ID__c for traceability.

Ascora job status values are mapped one-by-one to Pipedrive stage names in the target pipeline. 'Invoiced' jobs map to Won stage; 'Cancelled' or 'Declined' map to Lost stage; open statuses map to pipeline stages your team defines before migration. Probability weights are applied per stage during Pipedrive setup.

Ascora quotes with line items (materials, labor, parts) map to Pipedrive Products attached to the corresponding Deal. Each quote line item becomes a Product item with unit price and quantity. Quote totals are stored as the Deal's value. Accepted quotes trigger Deal stage advancement.

Ascora job activities (technician notes, parts used, service description) migrate as Pipedrive Activities. Each activity inherits the Deal and Organization linkage from the parent job. Original timestamps and assigned technician are preserved as activity metadata and custom fields respectively. Parts consumed during service visits are documented in the activity notes field for future reference and inventory tracking.

Ascora invoices track financial transactions tied to jobs. Pipedrive has no native invoicing object. We preserve invoice reference numbers and amounts as custom fields on the corresponding Deal and link the invoice PDF as a file attachment. Full invoice history should be maintained in your accounting tool (Xero, QuickBooks) post-migration.

Ascora custom fields built via the form builder (dropdowns, checkboxes, text fields) require matching Pipedrive custom fields to be created before data lands. FlitStack AI generates a Pipedrive custom field setup plan listing each field name, type, and entity assignment. Dropdown options are migrated value-by-value; checkboxes become Pipedrive boolean fields.

Ascora technician and admin users are resolved to Pipedrive users by email address match. Unmatched owners are flagged before migration — teams either invite them to Pipedrive first or assign records to a fallback user. Technician-specific fields (certifications, regions) migrate as custom fields on the User record where Pipedrive supports them.