Migrate from ASPEC to Microsoft Dynamics 365 Sales

ASPEC Contact records with name, email, phone, address, and owner assignment map directly to Microsoft Dynamics 365 Sales Contact. We extract all standard fields and write them to Contact using the Dataverse REST API. Owner resolution happens via email match against the destination Dynamics 365 User table. Any ASPEC Contact without a matching Dynamics 365 User is held in a reconciliation queue until the customer's admin provisions the corresponding User record.

ASPEC Company records map to Microsoft Dynamics 365 Sales Account. ASPEC Company IDs are preserved in a custom field aspec_company_id__c for cross-reference. Account is created before Contact import so that the CustomerId or ParentAccountId lookup is satisfied at the moment of Contact insert. Company name becomes Account Name, domain becomes Website, and any phone or address fields map to the corresponding Account address fields.

ASPEC Opportunities with deal name, value, stage, and expected close date map to Microsoft Dynamics 365 Sales Opportunity. Stage names from ASPEC are captured during schema discovery and mapped to Dynamics 365 StageName values under a pre-created Sales Process. Deal value maps to Amount, close date maps to CloseDate, and owner assignment maps to OwnerId via the User resolution step. Custom stage labels that do not match Dynamics 365 defaults are created as custom stage values before import.

ASPEC pipeline configurations (stage names and ordering) are captured during the schema discovery step. We pre-create a Microsoft Dynamics 365 Sales Process in the destination org that matches the ASPEC pipeline structure exactly, including custom stage labels and probability percentages. This configuration is deployed to Sandbox first, validated by the customer's admin, then moved to production before Opportunity import begins.

ASPEC Activity records (calls, emails, tasks, meetings) are timestamped and linked to Contact or Company records. We map them to Dynamics 365 Task and Appointment entities via the Dataverse API. Activity links are resolved by matching the ASPEC contact_id or company_id to the migrated Dynamics 365 Contact or Account ID. The original activity timestamp is preserved as ActivityDateTime on the Dynamics 365 record. Large activity histories (over 100,000 records) use the Bulk API 2.0 with batch chunking to avoid timeout.

ASPEC stores custom field definitions separately from record data in a metadata layer. We run a mandatory schema discovery step before any data is written, enumerating every active custom field, its data type, and its assignment (Contact, Company, or Opportunity). Custom fields are pre-created in Dynamics 365 as custom fields on the corresponding entity using the appropriate Dataverse field type (string, integer, decimal, picklist, boolean, datetime) before record import begins. Skipping this step means custom field values are silently dropped during import.

ASPEC Owner assignments on Contact, Company, and Opportunity map to Dynamics 365 User records. Resolution is by email match. Any ASPEC Owner with no matching Dynamics 365 User is flagged in the reconciliation report with the Owner name, email, and record count. The customer's admin provisions the missing Users in Dynamics 365 and signals ready before the final migration phase begins. Inactive or archived ASPEC users require the admin to decide whether to provision an inactive Dynamics 365 User or reassign those records to an active User.

ASPEC tags on Contact and Company records are preserved as label arrays. We map them to a Dynamics 365 multi-select picklist custom field (aspec_tags__c) on the Contact or Account entity. During scoping, the customer chooses whether to use multi-select picklist or to map tags to Dynamics 365 Topics with TopicAssignment records, which provides a different UX in the Dynamics 365 timeline. Tag strategy is confirmed before import.