Migrate from Ascora to Freshsales

Ascora customer records map directly to Freshsales Accounts. Business name, address, phone, and website transfer as standard Account fields. Multi-site customers in Ascora generate one primary Account in Freshsales with site details stored in custom fields or related Contact records.

Each contact person associated with an Ascora customer maps to a Freshsales Contact linked by AccountId. Primary contact role (site manager, accounts payable, decision maker) migrates as a custom field on Contact since Freshsales does not have a native role-label system beyond Contact titles.

Ascora sites (physical locations with addresses, site-specific notes, and equipment lists) translate to a combination of Account-level custom fields (site address, site type, site status) and a related Contact record for the site manager. Sites with heavy equipment lists become a custom Equipment object in Freshsales linked to the Account.

Active and quoted jobs in Ascora map to Freshsales Deals — deal name uses the job reference number and description, deal amount maps from job value, deal stage maps from job status (Quoted, In Progress, Completed, Invoiced). Historical jobs closed more than 90 days ago may map to Tasks on the related Account for activity audit rather than as open Deals.

Ascora quotes with line items become Freshsales Deals with associated Deal Products. Each quote line item (item description, quantity, unit price, tax) creates a Product record in Freshsales (if not already present) and links to the Deal. Quote status (Draft, Sent, Accepted, Declined) maps to a custom Deal field since Freshsales Deal stages are pipeline-specific.

Ascora invoices carry financial records that Freshsales does not natively track. Invoices migrate as Notes on the related Account with invoice number, date, amount, and status preserved. For full financial history, teams typically maintain the Xero or QuickBooks integration and use Freshsales for sales pipeline only.

Ascora equipment records (brand, model, serial number, install date, maintenance schedule) become a Freshsales custom object (Equipment) with a lookup relationship to Account. Equipment type and status become custom pick-list fields. For equipment sold as products, a corresponding Product record is also created in Freshsales.

Ascora custom form fields on jobs (safety checklist responses, specific trade data, compliance fields) require Freshsales custom fields created before migration. Blossom plan limits to 10 custom fields — Garden and above support up to 300. We create custom fields during the schema setup phase and map each Ascora field to its Freshsales counterpart by type (text to text, number to number, date to date).

Ascora operator and technician assignments on jobs map to Freshsales User records by email matching. Unmatched operators are flagged and assigned to a fallback user or preserved as a custom Deal field (Assigned_Technician__c). Freddy AI-powered assignments in Freshsales can then be applied post-migration.

Ascora supplier bills and inventory tracking do not have a Freshsales equivalent. These records migrate as Notes on the related Account for audit reference. Material cost tracking on jobs preserves as a custom field on the Deal if needed for margin reporting.

Inbound enquiries captured in Ascora's lead tracking map to Freshsales Leads directly. Lead source, name, contact details, and enquiry description transfer as standard Lead fields. If the enquiry converted to a job in Ascora, the resulting Deal links back to the original Lead via the Deal's Contact or Account.

Job photos and attachments from Ascora re-upload to Freshsales Files attached to the corresponding Account or Deal record. File size limits (Freshsales caps at 25MB per file) are enforced during migration. Inline images in notes are extracted and re-hosted as Freshsales Files.