Migrate from AutoText to Salesforce Sales Cloud

AutoText stores tone profile, formatting defaults, interaction preferences, and notification settings per user. We document these by extracting values from the Chrome extension UI during the scoping call and map them to Salesforce User custom fields (custom Text, Picklist, or Checkbox fields on the User object) for any preference that has a Salesforce equivalent. Preferences that have no Salesforce analog (such as AutoText-specific AI model behavior toggles) are documented on a per-user settings card with a manual-rebuild instruction for the destination.

AutoText brand voice profiles define tone, formality level, and phrase libraries per brand or persona. We extract the profile name, tone classification, and any custom phrases or templates stored in the profile. In Salesforce, these map to a ContentWorkspace (Library) folder per brand, with Email Templates and Content Documents structured by tone and use case (initial outreach, follow-up, objection handling). The profile metadata is preserved as a custom field on the Email Template record for reference.

AutoText snippet libraries contain user-created text blocks used for repetitive email composition. We extract every snippet by name, category, and body text. Snippets map to Salesforce Quick Text (for short, reusable responses accessible from the Activity timeline) and to Salesforce Email Templates (for longer, structured blocks that include merge fields and conditional content). We preserve the original AutoText category structure as Quick Text Categories and Email Template folder hierarchy in Salesforce.

AutoText Chrome extension settings include permission scopes (Gmail access, thread read), enabled or disabled features (paragraph completion, tone adjustment), keyboard shortcut mappings, and language model selection. We extract these from the extension manifest and chrome.storage.local during scoping and map them to documented manual steps in the Salesforce setup guide we deliver. For example, AutoText shortcut mappings that have no Salesforce equivalent are noted as non-transferable user habits rather than configured settings.

For AutoText Business tiers, admin-level team settings such as shared snippet libraries, team brand voice profiles, and default tone policies are documented. These map to Salesforce org-level defaults (default currency, fiscal year, country/triangle mapping), Salesforce Setup configurations (path assistant, list views, public groups), and a Salesforce ContentWorkspace per team for shared templates. Admin-level settings require Salesforce System Administrator credentials to configure.

AutoText's Google account OAuth scope (gmail.readonly, gmail.compose, gmail.modify) is documented during scoping. This scope grants AutoText access to Gmail threads for context ingestion. In Salesforce, there is no equivalent Gmail integration scope because Salesforce uses its own Email Sync feature (Exchange/Gmail integration) with OAuth 2.0. We document the AutoText OAuth scopes as a reference for the customer's IT team to review, and we note that re-authorization of Salesforce Gmail integration must occur separately. AutoText does not maintain an AppExchange listing or an authorized Salesforce connector.

AutoText suggestion history records which AI suggestions were accepted or dismissed per user. This data is stored in AutoText's local session cache and is not exposed via any export endpoint. We cannot extract it programmatically. We document it as a non-migratable asset and advise the customer's admin to inform users that suggestion history will be lost on uninstall. Users can expect to rebuild personalized suggestion quality at the destination over their first week of Salesforce use, as the AI model learns new writing patterns in the destination environment.

AutoText caches Gmail thread context (prior email content, dates, links, prior answers) locally to generate context-aware suggestions. This session-level cache is transient and evaporates on uninstall or Chrome profile reset. There is no export path. We document this cache as non-migratable and note that Salesforce Email Sync and Salesforce Inbox provide a different model for email threading—where emails are stored as EmailMessage records linked to Contacts and Opportunities, accessible for AI-assisted composition via Einstein AI or third-party writing tools integrated with Salesforce.

AutoText learns individual writing patterns over time, adapting its suggestions to match a user's tone, vocabulary, and structure preferences. This learned model is stored in AutoText's inference layer and is not exportable as a portable file or API response. We document the existence and scope of these learned patterns per user and recommend that the customer evaluate Salesforce Einstein Activity Capture and Einstein AI email compose features as the destination-side replacement. Einstein AI learns from user behavior in Salesforce over time, building a new writing model in the destination environment.

AutoText tone preferences (formal, casual, friendly, persuasive) and formatting preferences (default signature, link behavior, list formatting) are extracted from the extension settings and mapped to Salesforce Email Settings (My Email Settings) and a default Salesforce Email Template per user. We use Salesforce Quick Text for tone-specific quick replies and Email Templates for full-message templates that match each tone category.

AutoText keyboard shortcuts for accepting suggestions, dismissing suggestions, and triggering autocomplete are extracted from the Chrome extension manifest and user settings. Salesforce does not expose a shortcut customization API for email composition, but Lightning Experience provides standard keyboard shortcuts for navigation and record operations. We document the AutoText shortcuts on a per-user settings card and note which are non-transferable in Salesforce.

AutoText stores user email signatures and default closing phrases per user. We extract the signature text, HTML formatting, and any inline images. These map to Salesforce Email Templates with the signature baked into the template body, and to Salesforce User Email Settings (My Email Settings) where a default signature can be configured. If the signature includes dynamic merge fields, we recommend Salesforce Email Templates with appropriate merge field syntax rather than a static signature stored in User settings.

AutoText custom phrase libraries store user-defined abbreviations and their expansions (e.g., typing 'asap' expands to 'at your earliest convenience'). We extract the abbreviation-expansion pairs from the AutoText extension settings. In Salesforce, these map to Quick Text records with a shortcut and body, and to a Custom Metadata Type (AutoText_Phrase_Library__mdt) that allows Salesforce admins to maintain the library without data migration—each record is re-created manually in Setup with the abbreviation as the label and the expansion as the body.

AutoText Business tier shared snippet sets are accessible to multiple team members and managed by an admin. We extract the shared snippet set name, category structure, and all shared snippets. These map to a Salesforce ContentWorkspace (Library) shared across the team, with Email Templates and Content Documents organized by snippet category. Shared snippet access permissions are noted as a mapping to Salesforce ContentWorkspaceMember access levels.