Migrate from AutoText to Microsoft Dynamics 365 Sales

AutoText stores per-user tone, formatting, and interaction preferences that have no direct equivalent in Microsoft Dynamics 365 Sales . We extract these manually through screen-share review of the Chrome extension settings panel and document them as a written preference specification. The customer or their Dynamics 365 admin rebuilds equivalent settings using Dynamics 365 personal options (email signatures, default views, user settings) and Microsoft 365 user profile settings.

AutoText brand voice profiles (tone presets, formal/informal calibration, industry-specific terminology) store as named configurations with typed field values. We preserve these as a written brand voice specification document with structured field values that can be entered as custom fields on Contact or Account in Dynamics 365 (for example, tone_preference__c, communication_style__c, industry_terms__c). Microsoft Dynamics 365 Sales Copilot can then use these as context for AI-generated email content at the premium tier.

AutoText Chrome extension settings (enabled/disabled features, keyboard shortcut mappings, OAuth permission scopes, notification preferences) exist in Chrome local storage and Google account OAuth, not in a portable config format. We manually document these during a screen-share scoping session and produce a settings map that the customer's admin uses to configure equivalent preferences in Microsoft 365 and any Dynamics 365 user-level settings. This is a manual reconstruction, not an automated import.

If the organization uses AutoText Business with shared snippet libraries or team-admin settings, we extract these manually and map them to a written team-configuration document. Microsoft Dynamics 365 Sales does not have a direct equivalent to snippet libraries, but team-level templates can be configured as Microsoft 365 Word templates stored in SharePoint and attached to Dynamics 365 records, or as Power Automate templates for standard outreach sequences.

AutoText's Google account OAuth scope is documented but not migrated. At the destination, the customer authorizes Microsoft Dynamics 365 Sales and any related Microsoft 365 applications through the Azure Active Directory app registration portal. We note which Google integrations must be replaced with Microsoft equivalents (for example, Gmail-based AutoText suggestions replaced by Microsoft Dynamics 365 Sales Copilot in Outlook).

AutoText does not expose a public API for suggestion acceptance history. This data is not migratable and there is no Dynamics 365 equivalent. We do not attempt to reconstruct it. The Microsoft Dynamics 365 Sales Copilot AI builds its own suggestion model from Dynamics 365 activity data over time.

AutoText caches Gmail thread context locally for inference within the Chrome extension session. This ephemeral cache evaporates on extension uninstallation and has no export path. Microsoft Dynamics 365 Sales does not use thread-context caching; AI features operate on CRM data rather than email thread history. This data is not migratable.

AutoText does not store CRM records (Accounts, Contacts, Deals, Activities) because it is a writing assistant, not a CRM. Microsoft Dynamics 365 Sales is provisioned fresh with standard CRM schema. We flag that the migration scope does not include importing CRM records because none exist in AutoText. If the customer has CRM data in another system (even a spreadsheet), we can add that as a parallel migration scope.