Migrate from Function 365 to Microsoft Dynamics 365 Sales

Microsoft Graph API delegation scopes require admin consent before email and calendar read

Accessing mailbox contents via Microsoft Graph demands Application or Delegate permissions scoped to Mail.Read, Calendar.Read, and Contacts.Read. In tenant-scoped migrations, an admin must grant admin-consent to the FlitStack Azure app registration before Graph can enumerate email threads and calendar events. If your tenant has Conditional Access policies blocking third-party app access to Exchange, a fallback import method using PST exports or Exchange Online PowerShell may be required — this adds manual steps and extends the project timeline.

SharePoint file migration requires explicit consent and site-relative URL remapping

SharePoint document migration under Dynamics 365 Sales uses the connected SharePoint environment as the target. If your Function 365 SharePoint sites are in a different tenant or the site URL structure differs from the Dynamics 365 Sales SharePoint configuration, file URLs stored in Annotation records will point to the original source. FlitStack flags URL mismatches and offers re-hosting (downloading and uploading to the Dynamics-connected SharePoint) as a billable add-on, or preserves the original URL as an external document reference field on the Annotation.

Azure AD Object ID matching assumes UPN stability across the migration

Dynamics 365 Sales SystemUser matching to Microsoft 365 users relies on UserPrincipalName (UPN) or Azure AD Object ID. If your organization undergoes a tenant domain change (e.g., merging after an acquisition) or renames UPNs post-migration, owner lookups on migrated Activity records break. We recommend completing UPN normalization before scheduling the migration window. If UPNs have already changed, a post-migration owner re-mapping script can correct affected records. This script compares the Azure AD Object ID stored during migration against current Azure AD user records and updates the owner references in Dynamics 365 Sales accordingly.

Teams chat messages have no standard Dynamics 365 Sales entity and require custom table setup

Teams channel messages and direct chats lack a built-in Dynamics 365 Sales activity type. Storing Teams chat history requires pre-creating a custom Dataverse table (e.g., TeamsChatMessage) in your Dynamics 365 Sales environment with columns for message text, sender, timestamp, and regarding object lookups. This custom table must be provisioned before the migration run begins. If your compliance requirements demand preserving Teams chat for CRM audit purposes, budget additional configuration time for the custom table schema.

Email body HTML rendering varies between Exchange Online and Dataverse activity format

Microsoft Graph returns email body content as HTML or plain text depending on the prefer header. Dynamics 365 Sales Email activity description field accepts HTML but applies its own sanitization that can alter table layouts and embedded image references. We normalize email body content to a safe HTML subset during migration, preserving text formatting, links, and inline images where supported. Complex email templates with external CSS or VML elements may lose styling fidelity — this is documented in the pre-migration diff output.