Migrate from Ascora to Salesforce Sales Cloud

Ascora Customers map directly to Salesforce Accounts. Company name becomes Account Name. Physical address fields on the Customer record map to BillingAddress and ShippingAddress on the Account. Where the Customer is an individual rather than a business, the record maps to a Salesforce Contact with the AccountId lookup populated from the mapped Account.

Ascora Sites represent physical locations tied to a Customer. In Salesforce, each Site becomes either a child Account with ParentId pointing to the primary Account, or a Shipping Address on the Account record. Multiple Sites per Customer collapse to multiple Address records on a single Account — your admin chooses the preferred model before migration runs.

Ascora Customer contacts map to Salesforce Contacts with the AccountId lookup pointing to the parent Account. Email, phone, and mobile phone map directly. Job title and role information migrate as a custom field if Ascora stores it as a contact property.

Ascora Jobs are billable engagements tied to a Customer and Site. They map to Salesforce Opportunities with the AccountId lookup populated, CloseDate set from the job completion date, and Amount populated from the invoiced value. Job status (pending, in-progress, completed, invoiced) migrates as a custom pick-list field on the Opportunity.

Ascora job types (electrical, plumbing, HVAC, etc.) have no direct Salesforce equivalent. We create a custom pick-list field (Job_Type__c) on Opportunity and map each Ascora job type to a pick-list value. For distinct business-unit reporting, a Salesforce Record Type per job type is recommended — your admin pre-creates these before data lands.

Ascora Quotes tied to a Job map to the Opportunity record (using the same opportunity as the Job). Quote line items requiring granular tracking migrate to a custom Quote_Line_Item__c object linked to the Opportunity — or to Opportunity Products if the line items use Salesforce's standard product model. Your admin decides whether to use the standard Salesforce Quote object or a custom object based on your quoting workflow.

Ascora Invoices map to Salesforce Orders when Salesforce CPQ or Financial Services Cloud is in use. Without those products, Invoices migrate as a custom Invoice__c object linked to the Account and Opportunity, storing invoice number, date, total amount, and payment status. Original invoice PDF files are re-uploaded to Salesforce Files attached to the Invoice record.

Ascora Equipment records map to Salesforce Asset objects. Serial number, make/model, installation date, and warranty expiration map directly. The Asset is linked to the Account (customer) and optionally to the Site via a custom Site__c lookup. Maintenance history stored as Job records linked to the Equipment becomes Activity records on the Asset in Salesforce.

Ascora staff records map to Salesforce Users by email match. Unmatched staff members are flagged — your team invites them to Salesforce first or assigns records to a fallback User. Staff roles (electrician, plumber) migrate as a custom pick-list field on the User record since Salesforce stores roles separately in the Role Hierarchy.

Ascora custom form fields per object (Job Custom Details, Site Custom Fields, Customer Custom Fields) become Salesforce custom fields. The field type in Ascora (text, number, date, pick-list) determines the Salesforce field type. Pick-list fields in Ascora require value-by-value mapping to Salesforce pick-list values. We flag any field with a type not natively supported by Salesforce for manual review before migration.

Ascora file attachments on Jobs, Customers, or Invoices re-upload to Salesforce Files attached to the corresponding record. File size limits apply (Salesforce default 25MB per file). Inline images in notes are downloaded and rehosted. File association metadata (upload date, uploaded by) is preserved in Salesforce File metadata.