Migrate from AddressTwo to Odoo CRM

Discovery and scoping

We audit the AddressTwo account across record counts (Contacts, Deals, Activities, Notes, Tags, Campaign memberships), custom field definitions, owner assignments, and pipeline stage names. We pair this with an Odoo edition and deployment decision: CRM-only on Odoo.sh Starter (~$24.90/user/month) for straightforward migrations; Odoo ERP suite if the customer needs accounting or inventory alongside CRM; or self-hosted Community edition if the customer prefers one-time infrastructure cost over recurring SaaS fees. The discovery output is a written migration scope and a source data inventory noting any records requiring AddressTwo support assistance to export.

AddressTwo data extraction

We request a full account export from AddressTwo support (email to [email protected]) and simultaneously apply for the v2.0 API key. If the API key arrives within the scoping window, we extract via API with conservative 30-second batch staggering to account for undocumented rate limits. If API access is not granted, we rely on the support-provided CSV export supplemented by targeted API calls or direct interface export for specific record types. We run a de-duplication pass on all Contact records before processing to merge any duplicates created by AddressTwo's email BCC sync behavior.

Schema design and partner restructure

We design the destination schema in the customer's Odoo instance. This includes creating custom fields on res.partner and crm.lead for each AddressTwo custom field (via Odoo Studio or direct ORM), configuring crm.lead.team records (one per AddressTwo pipeline), creating crm.stage values with probability percentages mapped from AddressTwo stages, and setting up res.partner.category records for the tag taxonomy. The company extraction step runs before the main partner import to create is_company=True res.partner records for each unique company identified in AddressTwo's embedded company field. Schema is validated in the Odoo test environment before any data moves.

Owner reconciliation and user provisioning

We extract every distinct AddressTwo Owner referenced on Contact, Deal, and Activity records and match by email against the destination Odoo instance's res.users table. Owners without a matching user go to a reconciliation queue. The customer's Odoo admin provisions any missing users (active or inactive depending on whether the original AddressTwo user is still contributing data). Migration cannot proceed past the partner import step because user_id and company_id references on crm.lead require valid destination users and partner records.

Sandbox migration and validation

We run a full migration into the customer's Odoo test or staging environment using production-like data volume. The customer's admin reconciles record counts (partners in, leads in, activities in, notes in), spot-checks 20-40 random records against the AddressTwo source, and validates that the partner-company hierarchy and lead ownership are correct. Activity history linking (mail.message to res.partner) is verified by checking that the chatter widget on a sample of partners shows the correct historical timeline. Any mapping corrections are documented and applied before production migration begins.

Production migration in dependency order

We run production migration in record-dependency order: res.partner.company records first (is_company=True), then res.partner person records (is_company=False with company_id set), then crm.lead.team and crm.stage configuration, then crm.lead (with user_id and partner_id resolved), then mail.message activity history (with model and res_id resolved to the migrated partner IDs), then res.partner.category and mailing.mailing for tag and campaign data. Each phase emits a row-count reconciliation report before the next phase begins. We use Odoo's XML-RPC or JSON-RPC API with batch chunking and exponential backoff for activity history volume.

Cutover, validation, and rebuild handoff

We freeze AddressTwo writes during cutover, run a final delta migration of any records modified during the migration window, then enable Odoo as the system of record. We deliver the automation and report inventory document to the customer's admin team. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild AddressTwo workflows as Odoo automated actions inside the migration scope; that work is handled by the customer's admin or an Odoo implementation partner.