Migrate from Empire SUITE to Microsoft Dynamics 365 Sales

Empire Suite contact records map directly to the Dynamics 365 Contact table with field-level precision. Standard fields including email address, phone number, full name, mailing address, and job title translate using direct field-name alignment where possible. Any contact records that do not have a primary company association in Empire Suite link to a default placeholder Account record in Dynamics 365 to maintain referential integrity.

Empire Suite contacts flagged as unqualified prospects or early-stage leads split to the Dynamics 365 Lead table. Leads qualifying through a sales process convert to Contact + Account in Dynamics 365. The Empire Suite status field drives routing logic during migration.

Empire Suite company records map to the Dynamics 365 Account table. Parent-child company hierarchies in Empire Suite translate to the Parent Account lookup field. Multi-company associations per contact collapse to a primary AccountId with additional relationships surfaced in Account Contact Relationships.

Open deals migrate as Opportunities with name, amount, close date, and owner resolved by email match to Dynamics 365 SystemUser records. The Empire Suite pipeline stage maps to the Opportunity Stage option set per the sales process configuration. Historical stage-enter timestamps become custom datetime fields for reporting continuity.

Empire Suite pipeline definitions become Dynamics 365 Sales Process definitions tied to Business Process Flows. Each pipeline in Empire Suite maps to a named business process; stage names map to stage values in the associated process. Stages requiring custom probability or forecast category get re-applied post-migration.

Empire Suite engagement records — logged calls, emails, meetings, and notes — migrate to the corresponding Dynamics 365 Activity entity types. Original timestamps, owners, and Regarding lookups linking back to Contact, Account, or Opportunity are preserved. Attachment files re-upload to Dynamics 365 Notes or SharePoint document storage.

Empire Suite custom objects map 1:1 to Dynamics 365 custom tables with new_ prefix. Relationships between custom objects and standard entities (Contact, Account, Opportunity) become Dataverse lookup columns. N:N relationships in Empire Suite require a junction table in Dynamics 365 — we surface this in the mapping plan.

All Empire Suite custom fields on Contact, Account, Opportunity, and Lead objects become Dynamics 365 custom columns. Field types map to Dataverse data types: text to Single-Line Text, numbers to Whole Number or Decimal, dates to DateTime, pick-lists to Option Sets. Option set values require explicit value-by-value mapping.

Empire Suite owner assignments on records resolve by email match against the Dynamics 365 SystemUser table. Unmatched owners flag for your admin to either invite the user to Dynamics 365 or reassign to a fallback owner before migration. No record lands without a valid OwnerId.

File attachments on records re-upload to SharePoint-integrated document locations in Dynamics 365 or attached to Note records. File size limits apply (default 128MB per file in Dataverse). Inline images in notes are downloaded and rehosted in Dynamics 365 SharePoint storage.

Empire Suite workflow definitions, automation rules, and sequence logic do not have a migration path. We export workflow definitions as a structured reference document your Dynamics 365 admin uses to rebuild automations in Power Automate or the legacy workflow designer. This is disclosed upfront during scoping.

Empire Suite reports and dashboards do not migrate. The underlying data migrates so reporting can be rebuilt against Dynamics 365 data. FlitStack provides a data dictionary mapping source fields to destination columns to accelerate your report rebuild in Power BI or Dynamics 365's built-in reporting tools.