Migrate from APSIS One to Microsoft Dynamics 365 Sales

APSIS One Profiles map to Dynamics 365 Contacts for qualified buyers and known customers. Prospects and unknown contacts in APSIS One without a full CRM record map to Dynamics 365 Leads. We use the APSIS Profile's lifecycle stage attribute (if populated) and the presence of company data to determine the split: Profiles with a company name and qualified contact data become Contacts linked to an Account; anonymous or early-stage Profiles become Leads. The original APSIS Profile ID is preserved in a custom field apsis_profile_id__c for audit and cross-reference.

Standard APSIS One Attributes (email, firstname, lastname, phone) map to the corresponding Dynamics 365 Contact fields. Custom Attributes map to custom fields on Contact that we pre-create in the destination org before migration. APSIS One's attribute type system (string, number, date, boolean, list) maps to Dynamics 365 field types (Single Line of Text, Whole Number, Date Only, Two Options, Option Set). Attributes with no corresponding Dynamics field become custom fields with a apsis_attribute_ prefix for identification.

APSIS One Tags are flat string labels applied to Profiles. We preserve the full tag set and map tags to a Dynamics 365 multi-select picklist field on Contact if the tag vocabulary is under 150 unique values. For larger tag sets, we use a text field with comma-separated values and flag the tag strategy during scoping so the customer's admin can decide between picklist maintainability and searchability.

APSIS One behavioral Events (email opens, link clicks, form submissions, custom event types) have no direct Dynamics 365 equivalent. The standard approach is to create a custom TimelineEvents entity in Dynamics with fields for event_type, event_timestamp, event_properties (JSON), and a Lookup to the parent Contact. We export the event history in batches from APSIS One and upsert into the custom entity, preserving the full behavioral record. If the customer uses Microsoft Dynamics 365 Sales Premium with Conversation Intelligence, events may also link to the interaction timeline there.

APSIS One Segments (dynamic rule-based or static list-based) have no direct exportable equivalent in Microsoft Dynamics 365 Sales . We export the Segment definitions and member lists from APSIS One and rebuild them as Dynamics Marketing Lists (static membership). Dynamic Segment logic (rule-based audience construction) is documented and handed off for rebuild in Dynamics 365's segmentation capabilities or Power Automate-based audience refresh. Complex multi-condition dynamic segments require the longest rebuild time.

APSIS One Consent 2.0 records store consent flags and timestamps per channel (email, SMS, web) as Profile Attributes. We preserve consent records exactly by mapping them to Dynamics 365 Contact fields: Email Opt-In (boolean), Email Consent Date (date), SMS Opt-In (boolean), SMS Consent Date (date). These fields are critical for GDPR and CAN-SPAM compliance post-migration and must not be lost during cutover.

APSIS One maintains a bidirectional sync with Microsoft Dynamics 365, mapping CRM Contacts, Accounts, and Deals to APSIS Profiles. The sync state is not accessible via the public API. We export the current Profile data and the integration configuration, then re-establish sync by re-pairing the Dynamics integration in APSIS One and triggering a full resync to repopulate sync metadata. Any Deals mapped in APSIS One are exported as Opportunities and linked to the resolved Account.

APSIS One Sections are organizational units holding Segments and Flows. We map Section hierarchies to Dynamics 365 Business Units (for org-level security scoping) or to Teams (for sharing model scoping). The customer's Dynamics admin decides the mapping based on the existing security and team structure. Sections without a Dynamics equivalent are documented as organizational metadata requiring manual reorganization post-migration.