Migrate from AutoText to Nutshell

AutoText stores enabled features, keyboard shortcut mappings, and Chrome extension permissions in local storage and the Google account OAuth scope. There is no export endpoint. We document these settings during a scoping call by reviewing the installed Chrome extension manifest and OAuth consent screen, then map each feature to its Nutshell equivalent (e.g., AutoText's formatting shortcuts map to Nutshell's email template formatting options). Settings must be reconfigured manually in Nutshell by each user.

If AutoText users configured brand-specific tone, phrasing, or formatting profiles, we extract the field values during scoping (type, voice characteristics, placeholder patterns) and map them to Nutshell email templates. Nutshell supports rich-text email templates with merge fields; brand voice patterns are recreated as template content and stored with descriptive names matching the original profile labels.

AutoText stores per-user tone profiles, formatting preferences, and interaction settings. We document the preference field values and map them to Nutshell's user-level account settings where equivalents exist. Preference settings without a direct Nutshell equivalent (e.g., paragraph-completion aggressiveness) are flagged as non-transferable and noted for manual review.

If users created or imported contacts and companies within AutoText's Gmail sidebar or any connected spreadsheet workflow, we migrate these as Nutshell People and Organizations. The mapping is direct: name, email, company affiliation, phone, and any custom fields map to the corresponding Nutshell People fields. Nutshell's People object accepts CSV import via its REST API or bulk import UI.

AutoText does not expose a dedicated snippet library export, but users who built reusable text fragments may have stored them locally in the Chrome extension's cached data. We document any identifiable snippet content during the scoping call and map it to Nutshell email templates (for email-bound content) or task notes (for non-email workflow content). Users should also export any manually maintained snippet spreadsheets before uninstalling AutoText.

AutoText's Gmail OAuth scope (read/write access to emails for thread-context ingestion) is documented but not migrated—OAuth authorizations are destination-specific. We note which Gmail permissions AutoText held so that the Nutshell Gmail integration can be configured with equivalent scope. Nutshell's Gmail integration (available from its Chrome extension) must be authorized separately.

AutoText does not expose a public API for suggestion acceptance history. This data is not migratable and is not attempted. Accepted suggestion patterns are implicit in the user's Gmail behavior and will naturally surface in Nutshell's activity timeline as users compose emails through Nutshell's templates and logging features.

AutoText caches Gmail thread context locally to generate context-aware suggestions. This session-level cache is transient—it evaporates when the extension is uninstalled or the Chrome profile is cleared. We do not migrate thread context caches because they are not persisted in a portable format. Users should expect to rebuild thread-aware suggestion quality at Nutshell over their first week of active CRM use.