Migrate from Aweber to Odoo CRM

Aweber subscribers map to Odoo CRM crm.lead records. Each subscriber becomes a lead with the email as primary identifier, name split into firstname and lastname fields, and subscription metadata preserved in custom fields. Unsubscribed subscribers import as inactive leads with opt-out flags.

Aweber list membership translates to Odoo CRM tags applied to crm.lead records. Each unique Aweber list name creates a corresponding tag in Odoo. Subscribers belonging to multiple lists receive multiple tags, preserving all segmentation logic from Aweber's list structure. Tags are stored using the tag_ids many2many relationship on the lead object, allowing flexible tag management within Odoo's native framework.

Individual subscriber tags in Aweber translate directly to crm.lead.tag_ids in Odoo. Tags preserve behavioral flags, product interests, and lifecycle stage information. Odoo's many2many tag relationship supports unlimited tags per lead, enabling comprehensive subscriber categorization. The original tag name and source metadata are retained during the migration process.

Aweber custom fields per list become custom_char, custom_selection, custom_integer, or custom_date fields on the crm.lead object. Field type is inferred from Aweber's configuration. Odoo requires custom fields to be pre-created before data import — FlitStack generates the field creation plan.

Aweber campaigns map to crm.lead.campaign_ids, Odoo's built-in campaign tracking model. Campaign names and send dates are preserved during migration. For historical campaigns no longer active, the campaign record is created in Odoo with archived status to maintain the full audit trail of past marketing activities and enable historical reporting in Odoo.

Aweber open and click events import as note-type activities on crm.lead records. Each engagement event creates an activity with type 'Email', the campaign name in the description, and the original engagement timestamp from Aweber. This preserves engagement history within the lead record.

Aweber unsubscribes map to Odoo leads where opt_out = True, preventing use in marketing activities. The unsubscription date is stored in a custom field x_unsubscribe_date for reporting and compliance tracking. This ensures Odoo CRM's marketing suppression matches Aweber's list hygiene rules, maintaining consistent subscriber preferences across both platforms.

Aweber signup forms and landing pages are tracked in Odoo CRM via the source_id field on leads. The form or page name is stored as the source, enabling lead quality reporting by acquisition channel from Aweber campaigns. Source attribution helps sales teams prioritize leads based on their original entry point into the marketing funnel.

Active Aweber subscribers import as active leads with active = True in Odoo CRM. Bounced email addresses are flagged using x_bounce_count and the lead is set inactive to prevent sending attempts. Complained subscribers with spam reports receive an x_spam_flag custom field and inactive status for compliance, ensuring Odoo respects all suppression signals from Aweber.

Subscribers with company names in Aweber create res.partner records as parent accounts, linked via crm.lead.partner_id. The company becomes a parent partner, and the individual subscriber becomes a child contact under that account. This preserves Odoo's account hierarchy model, enabling account-based views and consolidated company-level reporting in Odoo CRM.

The original Aweber subscribe date is preserved as crm.lead.create_date in Odoo, using the original timestamp rather than the migration execution date. This maintains reporting continuity for subscriber tenure metrics and enables cohort-based segmentation analysis in Odoo's reporting engine, giving teams accurate historical context for each lead record.

The subscriber email address maps to email_from on crm.lead and email on res.partner for contact records. This serves as the primary identifier for deduplication logic, owner resolution, and lead-to-contact matching during migration and subsequent data synchronization between the systems.

Aweber workflows, sequences, and automation rules do not transfer to Odoo CRM. These platform-specific constructs require manual rebuild using Odoo CRM Actions and server actions. FlitStack provides a structured workflow audit export as a reference document for your Odoo admin.

Aweber email templates cannot be imported into Odoo CRM. Odoo uses its own mail.template system with different field structures. Teams should plan to recreate templates in Odoo; FlitStack can export Aweber template HTML as reference material for the recreation process.

Aweber's dynamic segments (based on tag combinations and field values) translate to Odoo CRM as a combination of tag_ids and team_id assignments. FlitStack documents the segment logic during discovery so your team can recreate segments as saved views or automation triggers in Odoo.