Migrate from e-shot to Microsoft Dynamics 365 Sales

e-shot Contacts map to Dynamics 365 Contact records. The Contact's email address is the dedupe key. We extract all standard e-shot contact fields (name, email, phone, address) and custom contact fields defined in Settings > Contacts field manager, mapping each to a typed Dynamics 365 custom field. The e-shot contact ID is preserved in a custom field eshot_contact_id__c for audit and reconciliation. Contacts import after Account creation so that the parent AccountId lookup is satisfied at insert time.

e-shot's contact field schema is fully customisable. We extract every custom field definition (name, type, merge-tag syntax *_fieldname_*) from the field manager and create equivalent typed custom fields in Dynamics 365 using the Dataverse API. Merge-tag fallback values from e-shot (* *_fieldname=fallback('text')_ *) are replicated as default values on the corresponding Dynamics 365 custom fields so that contacts without data render cleanly rather than exposing raw merge tags.

e-shot Campaign records (email subject, sender details, scheduling, content body) map to Dynamics 365 Campaign. The campaign name and status migrate as-is. HTML template body migrates as the Campaign's Description field or as a Document attachment for reformatting in a Dynamics 365-compatible editor. Campaign send date and recipient count migrate to support historical reporting.

Historical campaign analytics (opens, clicks, bounces, unsubscribes, delivery health) export from e-shot's analytics dashboard and populate the corresponding Dynamics 365 Campaign's tracking fields. We preserve the send date, open rate, click rate, bounce count, and unsubscribe count as static numeric fields on the Campaign record so that historical performance remains queryable in Dynamics 365 without external reporting tools.

e-shot email templates (HTML with embedded styles and merge tags) export as raw HTML files. We preserve the merge-tag syntax as source values so that when the customer rebuilds templates in Dynamics 365-compatible editors (Dynamics 365 Email Editor, Adobe Creative Cloud, or marketing tools like Mailchimp), the personalisation tokens can be re-enabled against the migrated custom fields.

e-shot contact preferences (subscription interests and opt-in status) migrate to Dynamics 365 Contact as either boolean custom fields or a multi-select picklist, depending on preference centre structure. The tier limit on active preferences (basic: 25, pro: 50, omni: unlimited) is a scoping flag: we export only the active preferences currently in use. HasOptedOutOfEmail migrates as the primary email opt-out flag on Contact.

e-shot Forms and the preference centre store contact choices and field inputs. Forms have no structural equivalent in Microsoft Dynamics 365 Sales as a native object. We export form definitions, field types, and associated preference data as a written inventory document. The customer's admin rebuilds forms in Dynamics 365 using Power Apps portals, SharePoint, or a third-party form tool; we do not migrate forms as functional records.

Automated Series are workflow-based email sequences with trigger conditions and delay steps. These have no direct Microsoft Dynamics 365 Sales equivalent; Sales automation in Dynamics 365 relies on Power Automate or Sales Insights, which are different architectural models. We deliver a written inventory of every active Automated Series with its trigger, conditions, steps, and recommended Power Automate equivalent. The customer's admin or a Microsoft partner rebuilds the sequences post-migration.