Migrate from Ascora to HighLevel

Ascora customers map directly to HighLevel Contacts. We preserve the customer name, email, phone, and address. The Ascora customer ID migrates as a custom field (Source_Customer_ID__c) for traceability and delta-run de-duplication. During migration, we also map the original created date to a custom field to preserve historical context.

When an Ascora customer has a company name, we create a HighLevel Company record and link the Contact via the Contact-Company association. The primary company links as AccountId; additional sites become Custom Object records. If a customer has multiple locations, each site is stored as a separate Job_Site__c Custom Object linked to the primary Company.

Ascora jobs are the core unit of work. We map them to HighLevel Opportunities with the job name as Opportunity Name, job amount as Amount, and job status mapped to an Opportunity Stage via value mapping. The full job description and service notes migrate as Opportunity Notes.

Ascora job statuses (Pending, In Progress, On Hold, Completed, Invoiced) map to HighLevel pipeline stages by your configured value map. We preserve the original status-entered timestamp as a custom datetime field for historical reporting. This timestamp helps you track when a job transitioned between stages, enabling accurate cycle-time analysis.

Ascora technician assignments on jobs have no direct HighLevel equivalent. We create a Task record on the Opportunity for the assignment and store the technician name in a custom field (Assigned_Technician__c). User resolution by email matches technician contacts to HighLevel users where applicable. If a technician cannot be matched, their contact record is preserved as a custom field for later user assignment.

Ascora quotes with line items map to HighLevel Opportunities with product line items attached. Each quote line item becomes an Opportunity Product record. Approval status migrates as a custom field (Quote_Approval_Status__c) since HighLevel lacks native quote approvals. You can filter opportunities by approval status to prioritize deals awaiting sign-off.

The Ascora quote grand total maps directly to the HighLevel Opportunity Amount field. Tax and discount amounts are preserved as custom fields (Quote_Tax__c, Quote_Discount__c) on the Opportunity. These custom fields allow you to reconstruct the full pricing breakdown in reports and dashboards without modifying the standard amount.

Ascora custom fields on jobs (e.g., property type, job priority, safety checklist flags) need custom field definitions in HighLevel. We identify all custom field types during audit and create corresponding Custom Object schemas or Contact/Opportunity custom fields before migration runs.

Ascora stores a separate job-site address distinct from the customer address. HighLevel has no native job-site concept. We create a Job_Site__c Custom Object with address fields and link it to the Opportunity via the Custom Object association feature. Each Job_Site__c record also stores site-specific notes and contact details for field technicians.

Ascora invoices have line items, payment status, and Xero/QuickBooks sync flags. HighLevel has no native invoice object. We create an Invoice__c Custom Object with line items, payment status, and a link to the originating Opportunity. Integration sync status migrates as a custom field.

Ascora file attachments on jobs (photos, signed forms, invoices) are downloaded and re-uploaded to HighLevel Files linked to the corresponding Opportunity or Contact. File size limits per HighLevel apply (standard limit 25MB per file). We preserve original file names and timestamps to maintain audit trails and ease of reference.

Ascora workflows fire on job status changes, quote approvals, and technician dispatch events. HighLevel workflows trigger on contact actions and pipeline stage changes. These are architecturally incompatible. We export all workflow definitions as JSON and deliver them as a rebuild reference for your HighLevel admin.