Migrate from AutoText to Pipedrive

AutoText stores tone, formatting, and interaction preferences per user in Chrome local storage. We document these preferences during the discovery session, then configure equivalent settings in Pipedrive User preferences (timezone, notification preferences, language) and any matching custom fields on the Person or Organization record. AutoText tone profiles do not have a direct Pipedrive equivalent; we document the field values for manual reference and recommend Pipedrive's Activity Types or Tags as a loose analog for tone categorization.

AutoText extension permissions, enabled/disabled features, keyboard shortcut mappings, and OAuth scope grants are documented from the Chrome extension manifest. These are mapped manually to Pipedrive's user preference equivalents: notification settings (email vs in-app), activity tracking preferences, and calendar sync options. There is no automatic migration of extension configuration—each setting is reconfigured manually by the user or the migration team acting as a documented guide.

AutoText brand voice profiles (if configured by the team) are documented as structured field values. We map these to Pipedrive Custom Fields (text, picklist, or multi-select depending on the profile structure) attached to the Person or Organization object, or to Pipedrive Tags for loose categorization. The customer chooses the strategy during scoping.

For AutoText Business tiers, admin-level team settings and any shared snippet libraries are documented and mapped to Pipedrive Team Management settings. Pipedrive supports team-based territory assignment, user role management, and shared reporting views. Shared writing snippets map to Pipedrive email templates if the team uses templated email outreach.

AutoText's Google account OAuth scope is documented during discovery. Pipedrive's native Google Workspace integration requires re-authorization of the Google account within Pipedrive Settings. We document the AutoText OAuth scope for the customer to reference, then guide the re-authorization of Google Calendar and Gmail sync within Pipedrive.

If the customer has manually tracked contact records in AutoText notes, spreadsheets, or linked Google Contacts, we extract those records and import them into Pipedrive Person using CSV or the native Import2 tool. Pipedrive Person maps directly to AutoText contact name, email, phone, and custom fields. The import sequence is Person after Organization so that the OrganizationId lookup is satisfied.

Company records tracked manually (in AutoText notes, Google Sheets, or another source) migrate to Pipedrive Organization. We extract by domain where available, match to existing Pipedrive Organizations by name or domain, deduplicate, and import. Organization is the first CRM object imported because Person records depend on it via the org_id field.

If the customer has deal or opportunity records tracked manually, we migrate them to Pipedrive Deal. Each Deal requires a resolved OrganizationId (from the Organization import) and an OwnerId (resolved by email match to a Pipedrive User). Pipedrive's pipeline stages are created before Deal import using the customer's stage names.

Meeting notes, call summaries, or task records tracked in AutoText or associated Google Calendar events migrate to Pipedrive Activity. Tasks map to Pipedrive Task with Status, Priority, and ActivityDate. Meetings map to Pipedrive Event with StartDateTime, EndDateTime, and Location. Activities are imported after Person and Organization so that the WhoId lookup resolves to the correct Person record.

If the customer has email templates stored in AutoText or associated Google Workspace, we document these for import into Pipedrive email templates. Pipedrive supports email templates with dynamic field merge tags (person.name, org.name, deal.value) that replace the context-aware suggestion workflow AutoText provided. The migration team sets up the template library during Pipedrive configuration.