Migrate from ActiveTrail to Microsoft Dynamics 365 Sales

ActiveTrail Contacts map to a Dynamics 365 Contact record, with a corresponding Account created for each unique organization. We determine Account creation by grouping contacts sharing a domain or an explicit organization field. The Account stores company-level data (industry, size, address), while the Contact stores individual-level data (name, email, phone, title). The Contact.AccountId lookup is set during migration.

For ActiveTrail contacts that have not been qualified into an organizational relationship, we offer a Lead creation option. Leads are appropriate when the customer wants to maintain a pre-qualification pipeline separate from the Account-Contact hierarchy. We create a Lead only when requested; by default all ActiveTrail contacts land as Contacts with a parent Account.

ActiveTrail Company records (if populated by the customer) map directly to Dynamics 365 Account. Company name becomes Account.Name, domain becomes Account.Website, and address fields map to BillingAddress or ShippingAddress. Company-to-Account is the anchor mapping: Accounts must be created before Contacts that reference them.

ActiveTrail Segments are dynamic contact groups built on filter conditions. We export segment membership (the snapshot of contacts in each segment at migration time) as a Static Contact List in Dynamics 365. We also export the segment definition as a written rule set for the customer's admin to rebuild using Dynamics 365 Marketing segments or a Power Automate flow that replicates the filter logic.

ActiveTrail tags are behavioral labels applied to contacts (e.g., webinar_registrant, high_engagement, sms_consent). We map them to Dynamics 365 custom fields. For a small number of high-value tags, we create a multi-select picklist field (activetrail_tags__c). For large tag vocabularies, we store tags as a comma-delimited text field for the customer's admin to later parse into a more structured format.

ActiveTrail Email Campaigns map to Dynamics 365 Campaign records. Campaign name, subject line, send date, and audience size migrate. CampaignMember records are created for each contact who was sent the campaign, with Member Status set to Sent. We do not migrate campaign design assets (HTML templates) as these require manual reconstruction in Dynamics 365 email editor.

Email open and click events from ActiveTrail migrate as Note records attached to the Contact. Each note records the campaign name, engagement type (opened or clicked), and timestamp. These appear as historical interaction notes in the Contact timeline, not as native Dynamics 365 engagement records. We clarify this distinction in scoping so the customer does not expect live campaign analytics in Dynamics 365.

ActiveTrail SMS Campaigns map to Dynamics 365 Campaign records. SMS-specific data (character count, phone number, send time) migrates as custom fields on Campaign or as Note records on the Contact. E.164 phone number normalization is applied during migration. SMS campaign engagement (delivered, failed, replied) migrates as Note records on Contact.

ActiveTrail Automation Journeys cannot be migrated as live-running workflows. The journey definition (triggers, conditions, delays, channel actions) is exported as a written blueprint document with step-by-step descriptions and a recommended Microsoft Dynamics 365 Sales automated flow or Power Automate equivalent. The customer's Dynamics 365 admin rebuilds the automation post-migration. Any time-sensitive delays reset on reactivation.

ActiveTrail Landing Pages built in the platform builder are exported as HTML or documented as written descriptions of layout, form fields, and integration points. We do not migrate landing pages as functional assets. We deliver a written blueprint for rebuilding in Dynamics 365 Marketing pages, Power Pages, or a third-party landing page tool.

ActiveTrail Signup Form definitions (field names, field types, list assignment, automation entry trigger) are exported as written blueprints. The form-to-list and form-to-journey connections are documented for the customer's admin to rebuild using Dynamics 365 Marketing forms or Power Automate.

ActiveTrail custom contact fields (text, number, date, dropdown) map to custom fields on the Dynamics 365 Contact object. Dropdown fields require a picklist value mapping between ActiveTrail options and Dynamics 365 picklist values. The customer must provision the custom field schema in Dynamics 365 before migration; we validate field existence and type before loading data.