Migrate from Entera to Microsoft Dynamics 365 Sales

Direct map. Entera contacts migrate to Dynamics 365 Contacts with all standard fields (name, email, phone, job title, address) preserved. Dynamics 365 requires an AccountId lookup on every Contact — if an Entera contact has no associated company, it lands on a default placeholder Account and your admin assigns the correct AccountId post-migration.

Direct map. Entera companies migrate to Dynamics 365 Accounts with name, website, industry, employee count, and annual revenue fields preserved. Entera's parent-child company hierarchy migrates using Dynamics 365's Parent Account field — circular references are flagged before migration commits so your admin resolves them in the destination.

Direct map. Entera deals map to Dynamics 365 Opportunities with deal name as Opportunity Name, amount as Estimated Revenue, close date as Close Date, and owner as OwnerId. The Deal Stage field requires a value-by-value mapping since Entera's stage names differ from Dynamics 365's Opportunity Stage pick-list values.

Transformed. Each Entera deal pipeline becomes a Dynamics 365 Business Process Flow rather than a native entity. Business Process Flows drive stage progression in the Dynamics 365 Sales interface and must be configured in the destination before Opportunity records can be created — we deliver a configuration plan before the migration data loads.

Value mapping. Each Entera pipeline stage name maps to a Dynamics 365 Opportunity Stage value. If the stage names do not match Dynamics 365 defaults, your admin defines the new stage values in the destination before migration. Stage-entered timestamps from Entera are preserved in a custom datetime field for reporting continuity.

Custom entity required. Entera's property-specific records (rental income, cap rate, address, occupancy status) have no standard Dynamics 365 equivalent. We create a custom Property entity in Dataverse before migration runs, map all property fields to custom fields on that entity, and preserve the Entera property-to-deal relationship as a lookup field on the Opportunity.

Direct map. Entera engagement records migrate as Dynamics 365 Tasks (calls, emails) and Appointments (meetings). Original timestamps, activity owners, and regarding_objectid links to the Account or Opportunity are preserved. Call duration and outcome from Entera map to custom fields on the Dynamics 365 Task.

Direct map. Entera notes migrate as Dynamics 365 Notes, preserving rich-text formatting when the note body contains HTML. Any inline images embedded in notes are downloaded and re-hosted in Dynamics 365's SharePoint document management system, with the SharePoint URL linked back to the note record, ensuring attachments remain accessible and properly displayed in Dynamics 365.

Direct map. Entera file attachments on deals, properties, or contacts migrate to SharePoint document locations linked to the corresponding Dynamics 365 Account, Contact, or Opportunity record. File size limits (default 10MB per file in Dataverse) are handled with chunking — we flag any file exceeding the limit before migration.

Custom field required. Entera custom fields on any standard entity map to Dynamics 365 custom fields. API field names use Entera's original naming convention translated to Dynamics 365's schema format (lowercase, underscores stripped). Field types are mapped type-by-type: text to Text, number to Whole Number or Decimal, pick-list to Option Set.

Transformed. Entera owner records are resolved by email match against Dynamics 365 SystemUser records. Owners with no matching Dynamics 365 user are flagged before migration commits — your admin either invites them to Dynamics 365 first or assigns their records to a fallback owner. No Opportunity or Contact lands without a resolved OwnerId.

Custom field required. Entera links deals to property records via an internal association. In Dynamics 365, this relationship is modeled as a lookup field (PropertyId) on the Opportunity record pointing to the custom Property entity. Both the Opportunity and the Property record must exist before this lookup can resolve, so Property records migrate before Opportunity records.