Migrate from m-savvy to Microsoft Dynamics 365 Sales

M-savvy Contacts map to Dynamics 365 Contact. We preserve all standard fields — FullName, Email, BusinessPhone, MailingAddress, LifecycleStage (as a custom field if the destination field does not exist) — and link each Contact to a parent Account after the Account import phase. Owner resolution happens by email match against the destination User table. Any Contact without a matching Account during migration is held in a reconciliation queue until Account IDs are available.

M-savvy Account records map directly to Dynamics 365 Account. The Account-Contact relationship is directional in Dynamics 365: Account is the parent, Contact is the child. We import Accounts before Contacts and use the m-savvy Company ID as the external key for deduplication. Industry, size, and billing address fields map to the equivalent Dynamics 365 Account fields. If m-savvy stores multiple address types (billing, shipping) per Company, we map the primary address to the Account Address fields and hold secondary addresses for Account Address configuration in Dynamics 365.

M-savvy Deals map to Dynamics 365 Opportunity. Dealstage maps to Dynamics 365 StageName against a Sales Process we configure before migration. CloseDate, Amount, and Probability transfer directly. If m-savvy stores a Closed-Won or Closed-Lost reason as a custom field, we map it to Dynamics 365 internal字段 or a custom field for loss and win reason analysis. Each Deal's associated Contact and Account resolve to the migrated ContactId and AccountId at migration time.

M-savvy Leads (distinct from Contacts in m-savvy's data model) map directly to Dynamics 365 Lead. Lead status and lead source from m-savvy map to Dynamics 365 Lead Status and LeadSource. If the customer converts Leads to Contacts in m-savvy, we preserve both the original Lead record and the converted Contact during migration. Lead owner assignment resolves by email match against the destination User table.

M-savvy pipeline definitions and custom stage names are read from the m-savvy schema via API during discovery. Each m-savvy pipeline becomes a Microsoft Dynamics 365 Sales Process linked to an Opportunity Record Type. Stage probability values migrate from m-savvy to Dynamics 365 probability fields with rounding to the nearest integer percentage allowed by Dynamics 365. We flag stage count or ordering differences that would require a redesign of the customer's sales process in Dynamics 365.

M-savvy activity records (calls, emails, meetings, tasks) linked to Contacts, Accounts, or Deals migrate to Dynamics 365 Task, Email, and ActivityPointer entities. We set the Regarding (object) lookup on each activity to the migrated ContactId, AccountId, or OpportunityId after parent record resolution. Activity timestamps and subject lines preserve. Call duration and disposition values migrate to custom Task fields where Dynamics 365 does not have native equivalents. Activity type is encoded via the ActivityTypeCode or TaskSubtype field.

M-savvy custom objects require manual schema discovery via live API during the scoping phase because m-savvy publishes no public schema reference. We enumerate every custom object type, its fields, and its data types, then build a destination Dynamics 365 custom entity with equivalent fields using the Dataverse schema editor. Custom object lookups to standard objects (Contact, Account, Opportunity) are preserved as Dataverse lookups, and parent-record resolution happens during the migration transform phase. We share the complete schema map with the customer for confirmation before any data moves.

M-savvy stores attachment files separately from record data and requires a separate file-export pass. We download files via the m-savvy file API, stage them locally, then upload to Dynamics 365 as Annotation records (for in-record notes and files) or SharePoint document locations linked via the Regarding field. Each file is relinked to its parent Contact, Account, or Opportunity by resolving the original m-savvy parent record ID to the migrated Dynamics 365 record ID. Attachments whose parent records failed migration are flagged and held for manual review.