Migrate from ASPEC to Salesforce Sales Cloud

ASPEC Contact records map directly to Salesforce Contact. Standard fields (Name, Email, Phone, MailingAddress, Title) migrate 1:1. Custom fields identified during schema discovery map to Salesforce custom fields with equivalent data types (text, number, date, picklist). The Contact's primary Company link in ASPEC (referencing a Company record by ID) is resolved to the AccountId lookup during migration after Accounts are inserted.

ASPEC Company records map to Salesforce Account. Company name becomes Account Name; website becomes Website; industry and phone migrate to equivalent fields. Account is inserted before Contact import so that AccountId is available for the Contact-to-Account lookup at the moment of Contact insert. ASPEC's company-address fields map to BillingAddress on Account.

ASPEC Opportunities map to Salesforce Opportunity with direct field mapping: Deal name to Opportunity Name, deal value to Amount, expected close date to CloseDate, stage label to StageName. Pipeline stage labels captured during schema audit are used to configure a Salesforce Sales Process with matching stage values before Opportunity import begins.

ASPEC pipeline stage names and order are captured during schema discovery and written into a Salesforce Sales Process as stage values with corresponding probability percentages. If ASPEC stages include custom labels (e.g., 'Proposal Sent', 'Negotiation'), these are created as Salesforce StageName picklist values rather than custom fields so that standard pipeline reporting works without modification.

ASPEC call activities map to Salesforce Task with TaskSubtype set to Call. Call duration, disposition, and any notes stored in ASPEC migrate to custom Task fields (call_duration__c, call_disposition__c). ActivityDate is set to the original ASPEC timestamp so that the Salesforce activity timeline reflects the correct chronological order.

ASPEC email engagements migrate as Salesforce EmailMessage records (storing the email body and headers) linked to a Task record (providing the activity timeline entry). WhoId on the Task points to the resolved Contact or Lead; WhatId points to the related Opportunity or Account. Email addresses that cannot be matched to a Salesforce Contact are stored with a flag for admin review.

ASPEC meeting activities map to Salesforce Event. StartDateTime, EndDateTime, and location migrate directly. Attendee information from ASPEC is stored in EventRelation records linked to the Event, pointing to the resolved Contact or User. Virtual meeting links stored in ASPEC notes migrate to the Event's Description field.

ASPEC standalone task activities map to Salesforce Task with Status, Priority, Subject, and ActivityDate preserved. Task completion status in ASPEC maps to Salesforce Task Status (Not Started, In Progress, Completed). The task owner in ASPEC resolves to Salesforce OwnerId via the User mapping established during owner reconciliation.

ASPEC tags applied to Contacts and Companies migrate as multi-select picklist values on the corresponding Salesforce field. If the customer uses tags for content or segment classification, they may alternatively choose Salesforce Topics with TopicAssignment records. The tag strategy is confirmed during scoping before migration begins.

ASPEC record owners are mapped to Salesforce User records by email address. Active ASPEC users with email matches in the Salesforce destination org receive their records directly. Inactive or archived ASPEC users without a matching Salesforce User are held in a reconciliation queue for the customer's admin to provision before record import resumes. OwnerId references are required on Opportunity and must be resolved before Opportunity import.

ASPEC custom fields are defined in a separate metadata layer and must be enumerated during the schema discovery step before any mapping or migration begins. Each active ASPEC custom field is created in Salesforce as a custom field on the corresponding standard object (Contact, Account, Opportunity, Task) with a matching data type. ASPEC per-user custom fields are consolidated into a single set of custom fields visible org-wide in Salesforce.

If the customer's ASPEC instance includes custom objects (defined during schema discovery), we create matching custom objects in Salesforce with the same API name plus the __c suffix. All custom fields, lookup relationships to standard objects, and validation rules are deployed to Salesforce before any data import begins. Lookup dependencies are resolved in dependency order so that parent custom objects are inserted before child records.