Migrate from AutoText to Odoo CRM

AutoText stores tone, formatting, interaction, and shortcut preferences per user in the Chrome extension's local storage. We extract these manually during the discovery call using the Chrome extension manifest and OAuth scope inspection, then create equivalent custom fields on Odoo CRM's res.users model (for user-global preferences) and crm.lead/crm.partner (for contact-level voice settings). Field types map from AutoText booleans and text values to Odoo selection fields, boolean fields, and char fields respectively. We set defaults based on the AutoText configuration and deliver a field-by-field mapping spreadsheet during scoping.

If the team uses AutoText to enforce per-contact tone profiles (formal, casual, technical), we extract the field values from the Chrome extension settings UI and create equivalent custom fields on crm.lead (for Leads and Opportunities) and res.partner (for Contacts and Companies) in Odoo CRM. Selection fields with predefined tone options replace the AutoText categorical settings. This mapping is configuration-only; no data transformation is required beyond a manual value transfer during discovery.

AutoText brand voice profiles (brand name, tone, vocabulary preferences, prohibited terms) map to custom fields on res.company for organization-level brand settings and res.partner for contact-level brand assignments. We extract profile names, tone settings, and custom vocabulary from the extension UI and create Odoo custom fields of the appropriate type (char, selection, text). The customer chooses whether brand assignments are set at the company or contact level during scoping.

AutoText snippet libraries (text expansions triggered by shortcut keystrokes) map to Odoo Mail Templates in the CRM module. AutoText has no bulk export API for snippets; we manually extract the snippet shortcuts and bodies during discovery using the Chrome extension manifest and extension storage inspection, then recreate them as Odoo Mail Templates with the appropriate qweb syntax or plain-text body. We deliver a Snippet Inventory spreadsheet during discovery and an Odoo template setup guide during migration.

AutoText Chrome extension settings (enabled and disabled features, keyboard shortcut mappings, permission scopes) have no standardized export format and reside in the extension's local storage and Google account OAuth scope. We document these manually from the installed manifest during discovery and create equivalent Odoo CRM configurations: custom user fields for shortcut mappings, automation defaults for suggestion triggers, and an Odoo Setup Guide documenting which AutoText permissions (Gmail read/write, Google Calendar sync) require re-authorization in Odoo.

For AutoText Business tiers, admin-level team settings and shared snippet libraries map to Odoo CRM organization-level configuration. Shared snippet libraries (team-wide text expansions) map to Odoo Mail Templates shared across the team via template access groups. Team-level writing style policies map to custom fields on res.company and to default values on crm.lead. We document all admin-level settings during scoping and configure the Odoo equivalents during migration.

AutoText's Google account OAuth scope and Chrome Web Store installation record are documented from the extension manifest but cannot be migrated because OAuth tokens issued to the AutoText extension are scoped to that specific client ID and are not transferable. We document which Google permissions AutoText holds (Gmail read/write, thread access) and provide a written guide for re-authorizing equivalent scopes in Odoo's Google Gmail integration and Google Calendar sync. Any AutoText-specific Google Workspace admin configurations (OAuth app approval, scope allowlisting) must be reconfigured in the Google Admin console for the Odoo OAuth app.

AutoText does not expose a public API for suggestion acceptance or rejection history. This data is not migratable and we do not attempt to reconstruct it. The suggestion history represents AutoText's learned inference patterns, not user-authored content, and has no portable equivalent. We document this limitation in the migration scope and advise the customer that AutoText's suggestion quality will not transfer to Odoo; writing automation quality at the destination must be rebuilt over the first few weeks of use.

AutoText caches Gmail thread context locally for inference purposes. This ephemeral session data is transient; it evaporates when the extension is uninstalled or the Chrome profile is cleared. It is not persisted in a portable format and cannot be migrated. We do not attempt to transfer thread context caches. The customer's team should expect to re-establish thread-aware writing automation quality at the destination over their first week of Odoo CRM use with their email client.

AutoText does not store Contacts, Companies, Deals, Opportunities, or Activities. If the customer needs these records in Odoo CRM, they must be sourced from an alternative system: Gmail contacts export, a prior CRM export, spreadsheets, or a separate data collection process. We scope this separately from the AutoText preference migration. We advise the customer during discovery whether their Odoo CRM implementation requires a concurrent CRM data migration and provide a separate scope and estimate for that work.

AutoText email signatures and writing footers (personalized sign-offs, title blocks, legal disclaimers attached to outbound emails) map to Odoo CRM's email signature defaults. We extract signature content from the AutoText Chrome extension settings UI during discovery and recreate them in Odoo as default values on res.users (user signatures for outgoing emails) and as part of Mail Templates for CRM-case outbound communications. We document signature block format preservation requirements during scoping.

AutoText preserves Gmail-native formatting (bold, italic, links, lists) through the suggestion acceptance workflow. These formatting rules have no structured storage in AutoText and are applied by the extension's rendering engine at the point of acceptance. We document the formatting behavior in the Odoo Setup Guide and ensure that Odoo Mail Templates are configured with matching formatting (qweb HTML for templates, plain text fallbacks for compatibility). We do not migrate formatting rules as a structured dataset because AutoText does not expose them as such.