Migrate from ASPEC to HubSpot

Direct 1:1 map. ASPEC contact fields (name, email, phone, title, address components) map to HubSpot's standard contact properties. We create HubSpot contacts and associate them with the migrated company record using HubSpot's association API. Owner resolution happens via email match against HubSpot users before the contact record commits.

Direct 1:1 map. ASPEC company records (name, domain, industry, employee count, revenue, address) map to HubSpot company properties. ASPEC parent-child hierarchies collapse to flat HubSpot companies — the top-level parent becomes the primary company, and child companies are created as separate HubSpot companies with the parent link preserved in a custom field (Parent_Company_ID__c) for reference.

Direct 1:1 map. ASPEC deals map to HubSpot deals with stage mapping applied. Each ASPEC deal stage name is mapped to a corresponding HubSpot deal stage value within the target pipeline. Amount, close date, deal name, and owner transfer directly. We create HubSpot deals and associate them with the migrated contact records using HubSpot's deal-contact association API.

ASPEC pipelines become HubSpot deal pipelines. If ASPEC uses a single pipeline model, we create one HubSpot pipeline. If ASPEC supports multiple named pipelines, we create corresponding HubSpot pipelines and map deal records into the correct pipeline based on their ASPEC pipeline assignment. Each pipeline requires stage value mapping before deal migration begins.

Stage names require value-by-value mapping since ASPEC stage labels (e.g., 'Proposal Sent', 'Contract Review') differ from HubSpot's default stage names (e.g., 'Qualification', 'Proposal/Price Quote'). We map each ASPEC stage to a HubSpot stage within the target pipeline. Stage probability and forecast category re-apply based on HubSpot's stage configuration. If ASPEC uses 10+ custom stage names, we recommend creating a HubSpot pipeline with custom stage values before migration.

ASPEC lifecycle or lead status fields have no direct HubSpot equivalent. We create a custom pick-list property (Lifecycle_Stage__c or Lead_Status__c) on the HubSpot contact and map ASPEC values to HubSpot's standard lifecycle_stage values where possible. ASPEC stages that don't match HubSpot's fixed values (subscriber, lead, MQL, SQL, opportunity, customer) are preserved as-is in the custom property. Original create dates and stage-transition timestamps are preserved as custom datetime fields for reporting continuity.

ASPEC engagement records (calls, emails, meetings, notes) migrate to HubSpot engagements with original timestamps and owners preserved. HubSpot engagements store the source system ID, engagement type, and timestamp. Notes migrate as HubSpot notes with body content and metadata. We preserve the association between each engagement and its parent contact or company record using HubSpot's engagement association API.

ASPEC owner and user records resolve to HubSpot users by email address match. We pull all ASPEC owner IDs assigned to contacts, companies, and deals, then cross-reference against HubSpot user emails. Unmatched owners are flagged before migration — your team either invites them to HubSpot or assigns their records to a fallback owner. Owner name and email transfer as custom properties on records for audit trail continuity.

ASPEC custom fields that have no HubSpot standard equivalent are created as custom properties on the relevant HubSpot object. Field type validation applies — if ASPEC stored mixed-type data (e.g., dates stored as text), we create the HubSpot property with a compatible type and flag any records that may fail validation. We audit ASPEC's custom field schema before migration and deliver a property creation plan so your HubSpot admin can pre-create the properties or approve our type selections.

ASPEC file attachments associated with contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files. Files are linked to the relevant CRM record using HubSpot's file association API. File size limits apply (HubSpot default 25MB per file for standard imports; larger files require manual upload or increased limits). Inline images in notes are extracted, downloaded, and re-hosted as HubSpot-hosted files.

ASPEC custom objects (if present in your schema) map to HubSpot custom objects. HubSpot custom objects are available on Enterprise tier — your plan must support them before migration. Custom object associations that use ASPEC's N:N relationship model need HubSpot junction objects or association properties. We deliver a schema plan showing the custom object structure, field mappings, and relationship translation before the migration runs.

ASPEC association labels between contacts and companies (e.g., 'Primary Contact', 'Billing Contact') have no direct HubSpot equivalent. HubSpot supports contact-company associations as a simple linked/unlinked relationship. We preserve association label names as a custom property on the contact record (Original_Association_Role__c) for reference. If your team needs role-based association filtering, HubSpot's Enterprise tier offers custom association types.