Migrate from ASPEC to Freshsales

ASPEC Contact records map directly to Freshsales Lead. Name, email, phone, address, and owner assignment migrate 1:1. ASPEC's per-user custom fields on Contact are enumerated during schema discovery and mapped to Freshsales Lead custom fields. If any ASPEC Contacts represent existing customers rather than prospects, they map to Freshsales Contact tied to an Account; we identify these by checking for associated Opportunities in ASPEC and apply the split during import.

ASPEC Company records map to Freshsales Account. Company name becomes Account Name; website, address, phone, and industry fields migrate directly. We use Company domain or name as the dedupe key during import. Account is created before any Contact import so that the Account lookup is satisfied at the moment of Contact insert. Company-Contact associations are preserved via the Account-Contact relationship in Freshsales.

ASPEC Opportunities map to Freshsales Deals. Deal name, value, stage, expected close date, and owner assignment migrate directly. ASPEC pipeline and stage names are captured during schema discovery and mapped to Freshsales pipeline and stage values, which we configure before any Deal records are imported. If ASPEC Opportunity has an associated Company, we write the Account lookup first so the Deal-Account link is satisfied.

ASPEC Activity records (calls, emails, meetings, tasks) migrate to Freshsales Tasks and Events. Call activities map to Task with Task Subtype set to Call and duration preserved in a custom field. Meeting activities map to Event with start and end time preserved. Email and task activities map to Task. All activity records are linked to the parent Contact or Company via Freshsales' WhoId and WhatId fields after those records have been imported. Activity timestamps are preserved to maintain the historical timeline.

ASPEC custom fields exist in a separate metadata layer and are not stored with record data. We run a mandatory schema discovery step before any data import to enumerate every active custom field on Contact, Company, and Opportunity, capturing field name, type, and any validation rules. We then pre-create matching custom fields in Freshsales for the appropriate object (Lead, Contact, Account, Deal). Note that Freshsales imposes per-plan custom field limits: Growth at 15, Pro at 25, Enterprise at 50 custom fields per object.

ASPEC User records map to Freshsales Users. We match by email address, which must exist as an active user in the Freshsales destination org. Any ASPEC User referenced as an owner on Contact, Company, Opportunity, or Activity records without a matching Freshsales User is flagged in the reconciliation report for the customer's admin to provision before record import resumes. Archived or inactive ASPEC users are imported as inactive Freshsales Users for historical ownership preservation.

ASPEC Tags on Contact and Company records migrate to Freshsales Tags. Tags are stored as string arrays and written to Freshsales' Tag field on the respective object. We preserve the full tag set per record during import. Freshsales tags are case-sensitive and flat; any hierarchical tag structures in ASPEC are flattened to the most granular tag value.

ASPEC Pipeline stages are captured during schema discovery and mapped to Freshsales Pipeline and Stage configuration. We create the Freshsales pipeline and its stages before importing any Deal records, mapping each ASPEC stage name to an equivalent Freshsales stage with matching position order. ASPEC stage probabilities are recorded and can be optionally mapped to Freshsales stage weights if the customer requires probability-based forecasting in Freshsales.