Migrate your Ascora data

Customer records include contact details, addresses, billing info, and site associations. We map these to the destination CRM's Contact/Account object. Phone, email, and address fields are standard; custom fields require field-level mapping against Ascora's Custom Forms schema.

Sites are property/location records linked to Customers. We preserve the site-to-customer relationship as a related object or sub-record depending on the destination schema. Multi-site customers may have several site records that need careful 1:many mapping.

Equipment records are tied to Sites and track appliances, systems, or assets at a location. We map Equipment to the destination's equivalent sub-object (often a custom Equipment or Asset object). Serial numbers, model numbers, and service history are carried across as properties.

Leads capture enquiries from websites, phone calls, and Facebook. We export Lead records with source attribution, status, and contact info. Where the destination CRM uses a separate Lead object, we land these as standard Leads; otherwise we merge into Contacts and preserve source metadata.

Quotes are built from item libraries and price books, then sent as branded templates. We export quote line items, pricing, and status. Because line-item structures vary by quote, we flatten them into a standard format (item name, quantity, unit price, total) for destination import.

Jobs are the core operational record linking technician, site, equipment, quote, and custom form data. We sequence Jobs with their status history, assigned technicians, and timestamps. Custom form responses attached to Jobs require extraction from Word template field codes and are mapped as custom properties.

Invoices are linked to Jobs and synced to Xero, MYOB, or QuickBooks. Where a two-way sync exists, we flag whether the destination is a source-of-truth accounting system. We export invoice line items, totals, tax codes, and payment status for recreation in the target.

Custom Forms use Word document templates with field codes (e.g., {Project Sign Off By}) to generate technician-completed documents in the mobile app. We extract field codes as structured key-value pairs rather than the rendered document, mapping them to custom fields in the destination CRM.

User and technician records include names, roles, and schedule assignments. We map Users to Owner or Assignee fields in the destination. Where technician-specific scheduling data (zones, skills, availability) exists, we treat it as custom properties.

Item libraries feed Quotes and Invoices with part numbers, descriptions, and pricing tiers. We export the full price book as a line-item reference table, preserving unit costs and mark-up rules so destination item records can be rebuilt with pricing intact.