Migrate from AutoText to Mailchimp

AutoText stores tone, formatting, interaction, and brand voice preferences per user. These map to Mailchimp Brand Content assets and Audience settings (default from name, reply-to address, campaign defaults). We extract the preference field values during manual review and map them to the closest Mailchimp equivalent. Any preference with no Mailchimp analog (for example, AutoText-specific shortcut mappings) is documented in the preference inventory as non-transferable and flagged for manual rebuild.

If the AutoText user has configured brand-specific writing profiles (tone, formality level, signature blocks, approved phrases), we capture these as structured text and map them to Mailchimp email templates and brand content. Mailchimp does not have a native brand voice profile object, so we convert the AutoText profile to a written brand guidelines document attached to the Mailchimp audience as a custom field or shared with the customer as a configuration reference for template authoring.

AutoText Chrome extension permissions, enabled/disabled features, keyboard shortcut mappings, and OAuth scope are stored in the extension manifest and Chrome local storage. We manually document these during the scoping call and crosswalk them to Mailchimp equivalent settings where they exist. AutoText shortcut mappings have no Mailchimp equivalent; we document them for the customer's awareness. The Google account OAuth scope (which grants AutoText Gmail access) does not transfer—Mailchimp uses its own API credentials for sending, which are configured separately.

For AutoText Business tier deployments with team-wide settings, shared snippet libraries, or admin-configured preferences, we map the organizational configuration to Mailchimp workspace structure and team roles. Mailchimp workspace roles (Admin, Manager, Author, Viewer) map to AutoText team permission levels if applicable. Shared snippets map to Mailchimp content studio assets (image library, file storage) as a content reference.

AutoText's Google account OAuth scope (for Gmail thread ingestion) is documented but not migrated because Mailchimp does not require Gmail OAuth for sending campaigns. Mailchimp sends via its own mail transfer infrastructure. We document which integrations were active in AutoText and map them to Mailchimp equivalents where available: Google Workspace integration for contact management, Shopify for e-commerce subscriber capture, Zapier for broader automation routing.

AutoText does not maintain subscriber lists; it is a writing tool for individual email composition. If the customer has been using AutoText in conjunction with a separate subscriber management system (for example, collecting responses to AutoText-assisted emails), we migrate those contact lists to Mailchimp audiences. We map email addresses, subscriber status, and any custom fields to Mailchimp contact schema. Suppression lists (unsubscribed, bounced) from the prior email system are imported as Mailchimp suppression audiences before new contacts.

AutoText does not expose suggestion history or accepted-suggestion logs via API. This data is not migratable. We do not attempt to reconstruct it. Mailchimp does not have an equivalent data structure for AI writing suggestions. The customer should expect to build fresh engagement with Mailchimp's built-in AI subject line and content tools (Mailchimp's AI-powered subject line generator and content optimizer) as a functional replacement for AutoText's predictive suggestions.

AutoText caches Gmail thread context locally in the Chrome extension for session-level suggestion relevance. This cache is transient and non-portable—it evaporates on extension uninstall or Chrome profile clear. We do not migrate thread context caches. Mailchimp does not use thread context; it operates on audience-level campaigns rather than individual email thread analysis. The customer should expect to rebuild thread-aware suggestion quality through Mailchimp's campaign performance analytics over the first weeks of use.