Migrate from Resulticks to Microsoft Dynamics 365 Sales

Resulticks Contacts migrate 1:1 to Microsoft Dynamics 365 Sales Contact records. Standard profile fields (firstname, lastname, email, phone, address) map directly to their Dynamics counterparts. Custom contact properties are inspected during scoping; each is mapped to a native Dynamics field or a custom field (custom fields created via maker.powerpages.com before migration). Owner assignment uses email-to-User lookup. Records without an email address are held in a reconciliation queue because Dynamics 365 Contacts require an email for duplicate detection and activity routing.

Resulticks Contacts with lifecycle stages indicating unconverted prospects (subscribers, event registrants, cold inbound leads) are candidates for Salesforce Lead rather than Contact. We apply a split rule defined during scoping: Contacts with no Opportunity association and lifecycle stage below a defined threshold map to Lead. All Contacts and Leads are created in the same migration run with the split applied as a transform. Original Resulticks lifecycle stage is preserved in a custom field rs_lifecycle_stage__c on both Lead and Contact.

Resulticks audience definitions are rule-based (Contact attribute conditions and event conditions). Since Microsoft Dynamics 365 Sales does not have a native segment engine, we reconstruct segment membership by tagging each Contact with the segment name in a custom multi-select picklist field (rs_segments__c) or by creating static Marketing Lists. The customer chooses during scoping. Segment rule logic is documented in the handoff package for manual recreation as a Dynamics Marketing List or Power Automate flow.

Resulticks Campaigns migrate to Microsoft Dynamics 365 Sales Campaign. Campaign name, status, channel assignment, and scheduling migrate directly. Channel type (email, SMS, push, WhatsApp, web) maps to Dynamics Campaign Type. Budgeted cost and actual cost migrate to the corresponding Dynamics fields. Campaign content (body copy, images, templates) does not export from Resulticks and requires separate content export; we flag this during discovery. Campaign member associations migrate as CampaignMember records linked to the migrated Leads and Contacts.

Resulticks Tags migrate as a text multi-select or comma-delimited string in a custom field rs_tags__c on the Contact record. Microsoft Dynamics 365 Sales does not have a native tag object. Tag counts and distribution are preserved at the Contact level for segmentation and reporting purposes. If the customer uses tags for marketing segmentation, we recommend recreating tag groups as Marketing Lists in Dynamics.

Resulticks Users migrate to Microsoft Dynamics 365 Sales User records by email lookup. Any Resulticks User without a matching Dynamics 365 User is placed in a reconciliation queue for the customer's admin to provision before record import proceeds. Role and permission assignments are noted in the handoff package but require manual configuration in Dynamics security roles.

Resulticks custom contact properties (date fields, multi-select values, computed fields, legacy field types) are inspected during scoping. Each custom property is mapped to a typed Dynamics 365 custom field created in a pre-migration sandbox validation. Multi-select values map to Dynamics multi-select picklists; date-derived fields map to Date fields; computed fields require manual formula or workflow recreation in Dynamics.

Resulticks event history (page views, email opens, purchase events, custom track events) migrates within a configurable event window agreed upon during scoping. Due to schema variability and volume, we create a custom activity entity in Dynamics 365 (rs_event_history__c) to store the normalized event data with fields for event_type, event_date, source_channel, and event_payload. Event counts per Contact are summarized as rollup fields on the Contact record. Full event history migration beyond 90 days requires extended API calls and is scoped as an optional add-on.

Resulticks Journey flows are not exportable via documented API. During discovery, we photograph and document the full Journey map including branching logic, wait conditions, AI-driven decision nodes (Genie), and multi-channel node sequences. This documentation is delivered as a written handoff package for the customer's admin to rebuild in Microsoft Dynamics 365 Sales using Power Automate, Copilot Studio, or Dynamics out-of-box automation. Content within Journey nodes (copy, images, offer codes) requires separate content export from Resulticks.