Migrate from AddressTwo to Twenty CRM

Data export and scoping

We contact AddressTwo support on the customer's behalf to request an API key and a full account data export. We audit the export scope — confirming which objects (Contacts, Deals, Activities, Notes) are included and which custom fields are present — and compare against what we can retrieve programmatically if the API key is granted. We run a row-count reconciliation across all objects and identify any gaps (typically missing activity history or attachments). The scoping output is a written data inventory and a recommendation on extraction method (API or CSV-assisted).

Twenty workspace preparation

We configure the Twenty CRM destination workspace before any data arrives. This includes creating all required custom fields on Person and Opportunity objects, setting up Organization records if any exist in the initial workspace, configuring Opportunity pipeline stages to match AddressTwo's stage names, and verifying timezone and currency settings. If the customer is self-hosting Twenty, we confirm the self-hosted instance is provisioned and the API endpoint is accessible before migration scripts are written.

Company data extraction and Organization reconstruction

We extract the company name, website, and address fields from every AddressTwo Contact record and build a deduplicated Organization list. Each unique company name becomes one Organization record in Twenty. We then link each Person record to the corresponding Organization via the Person's companyId field. This step runs as a pre-import transform so that Organization records exist before Person records are loaded, satisfying the foreign key constraint. We validate the Organization count against the customer's expected count and reconcile any Contacts with no company name (which receive no Organization link).

De-duplication pass and data quality

Before importing Contact records into Twenty, we run a fuzzy de-duplication pass on the exported Contact dataset. We match on email address as the primary key and on company name as a secondary signal to catch any duplicate records that originated from AddressTwo's BCC sync behavior. We also flag Contacts with missing required fields (no email, no name) for customer review and correction before import. This step prevents duplicate Person records from entering Twenty and avoids broken Organization linkages.

Production migration in dependency order

We run production migration in record-dependency order: Organizations (from the extracted company list), Persons (with OrganizationId resolved), Opportunities (with PersonId and OwnerId resolved), and Activities (as timeline entries on each Person). Custom fields migrate last after the base object schema is validated. Each phase emits a row-count reconciliation report and we run a spot-check of 25-50 records against the AddressTwo source before advancing to the next phase. Owner resolution happens via email mapping; any Owner without a matching Twenty user is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Cutover, delta sync, and delivery handoff

We freeze AddressTwo writes during the cutover window, run a final delta migration of any records modified during the migration, and verify the row counts match between AddressTwo source and Twenty destination across all objects. We deliver the full migration report including record counts, mapping decisions, any unmapped fields flagged for customer review, and the written automation inventory for the customer's admin to rebuild in Twenty's workflow builder. We support a 48-hour hypercare window for reconciliation issues raised by the customer's team.