Migrate from AutoText to Freshsales

AutoText stores tone, formatting, and interaction preferences per user. Freshsales has no native equivalent for writing-assistant preferences because it is a CRM not a writing tool. We extract and document these preferences during the scoping call, then either populate Freshsales Contact custom fields (e.g., preferred_tone__c, communication_style__c) or deliver them as a written settings inventory for the customer's admin to use when configuring any Freshsales email templates or workflow triggers that reference communication style.

AutoText Chrome extension permissions, enabled/disabled features, and keyboard shortcut mappings are documented manually from the installed extension manifest. Freshsales has no Chrome extension equivalent—web access is browser-native. We document the AutoText settings in a written handoff sheet so the customer's admin can evaluate which, if any, have equivalents in Freshsales (e.g., email templates, keyboard shortcuts in the Freshsales mobile app). There is no programmatic transfer of extension configuration.

If the customer has configured brand-specific writing profiles in AutoText Business, we preserve the field values (tone labels, default phrases, approved terminology) in a written brand voice reference document. These do not map to a Freshsales native object because Freshsales email templates are content containers rather than AI-assisted writing profiles. The brand voice reference is handed to the admin to inform Freshsales email template setup.

AutoText Business team settings (shared snippet libraries, team-level tone profiles, admin controls) are reviewed and documented from the team admin console. Freshsales admin settings (user roles, permission sets, territory management, pipeline configuration) are configured from scratch as part of the Freshsales setup. We map the organizational intent captured in AutoText Business settings to Freshsales equivalents (e.g., team-based snippet libraries map to Freshsales Sales Docs or custom email template folders with role-based access).

AutoText does not store CRM records (Contacts, Companies, Deals). If the customer has CRM data in a secondary source—a spreadsheet, another CRM, or an existing Freshsales instance they are consolidating into—a separate data extraction and import engagement handles that layer. We scope this separately during discovery and apply standard Freshsales field mapping and import tooling (Admin Settings > CRM Data Import) for the CRM data layer.

AutoText's Google account OAuth scope and Chrome Web Store installation record are documented but not migrated. Freshsales connects to Google Workspace via its native Google Workspace integration, which requires separate OAuth authorization. We document which Google permissions AutoText currently holds and note the equivalent Freshsales permissions the admin must authorize during Freshsales Google Workspace setup.

AutoText does not expose suggestion acceptance history through any API or export mechanism. This data is not migratable. We do not attempt to reconstruct it. Users should expect to rebuild AI-assisted writing quality at the destination over their first week of use as Freshsales Freddy AI learns their communication patterns.

AutoText caches Gmail thread context locally for inference. This session-level cache is transient and evaporates on extension uninstallation or Chrome profile clearing. Freshsales does not ingest email thread context for AI suggestions—its Freddy AI assistant works from CRM record data and activity history. Thread-context suggestion capability does not transfer; the customer should evaluate Freshsales Freddy AI's deal insights and contact intelligence as the replacement signal source.