Migrate from Aweber to Microsoft Dynamics 365 Sales

AWeber subscribers map to Dynamics 365 Contacts. The email address is the primary deduplication key. If a subscriber lacks a company association, they land in a default 'No Account' placeholder record with a note. Original AWeber subscriber ID is stored in a custom field for delta-run traceability.

AWeber archived subscribers who have not explicitly opted out route to a Dynamics 365 Lead record rather than Contact, since they represent a lapsed prospect rather than an active contact. Active subscribers with no sales record also route to Lead by default unless a company association exists.

AWeber lists do not map 1:1 to any CRM entity. FlitStack AI treats the primary list associated with a subscriber as a signal for organizational affiliation. If a subscriber belongs to a single dominant list that represents a company, that list name becomes the Account name. Subscribers belonging to multiple lists are mapped to a primary Account with secondary list memberships preserved as custom text fields.

AWeber tags are free-form string labels attached to subscribers. They are migrated as a comma-delimited text field on the Contact record (AWeber_Tags__c) by default. If you have fewer than 50 unique tags and need segmentation, we can create a custom Tags table with a N:N junction to Contact and populate each tag assignment as a row.

AWeber allows up to 25 custom fields per list. Each unique custom field becomes a custom column on the Dynamics 365 Contact table. Field type mapping: AWeber text → Dataverse SingleLine.Text, AWeber number → Dataverse Whole.Number, AWeber date → Dataverse DateAndTime, AWeber dropdown → Dataverse Choice. Fields are suffixed with __c to follow Dataverse conventions.

AWeber campaigns have no native Dynamics 365 equivalent. The campaign name, send date, and total recipient count are preserved as a custom entity (AWeber_Campaign__c) linked to the Contact. Individual open/click events are stored as custom activity records rather than native campaign membership.

AWeber's Stats API returns per-subscriber open and click timestamps. These migrate as completed Task records attached to the Contact — Task with Type='Email Open' or 'Email Click', with the original timestamp and a reference to the source campaign name stored in the description field. This preserves the engagement timeline without creating native Dynamics campaign membership records.

AWeber signup forms are HTML form configurations that cannot be transferred to Dynamics 365. We export the form field definitions and configuration JSON as a reference document so your Dynamics admin can recreate equivalent intake forms using Dynamics 365's native forms designer or Power Pages.

AWeber email templates are HTML email bodies with merge tags. Dynamics 365 has an Email Template entity that supports similar merge-field syntax but uses a different token format. We export AWeber templates as raw HTML files and document the merge tag mapping so your team can rebuild templates in Dynamics Email Templates or Power Automate.

AWeber automations (triggers, conditions, action sequences) are workflow definitions stored in AWeber's platform. They do not migrate to Dynamics 365. We export the automation definition JSON from AWeber's API as a structured reference document and provide a mapping guide that translates AWeber triggers and conditions to Power Automate connectors and triggers.

Dynamics 365's CreatedOn timestamp is set at migration time, not at the original AWeber subscription date. To preserve reporting continuity on how long a contact has been in your ecosystem, we store the original AWeber createdate as a custom datetime field on the Contact record.

AWeber subscriber billing addresses map to the postal address block on the related Dynamics 365 Account record. AWeber stores address1_line1 through address1_postalcode as standard fields. These map to address1_line1 through address1_postalcode on the Account using Dynamics' composite address structure. If the subscriber has multiple address entries, the primary billing address is selected; additional addresses are stored as custom text fields on the Contact for reference.