Migrate from AddressTwo to Salesforce Sales Cloud

Scoping and AddressTwo data request

We audit the AddressTwo account for record counts across Contacts, Deals, Activities, Notes, and campaign membership, and we identify custom field definitions by asking the customer to share their field setup. We submit a formal data export request to AddressTwo support on the customer's behalf, requesting the full account export including all available objects and fields. In parallel, we begin Salesforce destination configuration: defining the Account-Contact relationship model, identifying Deal pipeline stages, and identifying any custom fields required. If the AddressTwo API key is available, we begin API exploration to validate export scope. If the API key is delayed, we coordinate the CSV export path with AddressTwo support and continue Salesforce configuration on the extracted data.

Data extraction and deduplication

We extract the data from AddressTwo via API (if key granted) or via the support-provided CSV export. The exported Contact records are run through a de-duplication pass that identifies records sharing the same email address and merges them into a single entry with combined activity history before loading into Salesforce. The distinct company names from the Contact company field are extracted and prepared as Account insert records. Deal records, Activity records, and Notes are validated for required field completeness and flagged for manual review if the export is incomplete.

Mapping design and Salesforce schema deployment

We design the field mapping document covering every AddressTwo object to its Salesforce equivalent, including custom field creation specifications, Record Type assignments per Deal pipeline, and the Deal stage-to-Opportunity stage matrix approved by the customer. We deploy the Salesforce schema (custom fields, Record Types, Sales Processes, Page Layouts) into a Sandbox via metadata API or change set before any data moves. The mapping document is reviewed and signed off by the customer's Salesforce admin before production migration begins.

Sandbox migration and reconciliation

We run a full migration into the customer's Salesforce Sandbox using the extracted production-equivalent data volume. The customer reconciles record counts: Accounts in, Contacts in, Opportunities in, Tasks and Events in, Notes in. We spot-check 25-50 random Contact and Deal records against the AddressTwo source to verify field accuracy. The customer signs off on the Sandbox results before we proceed to production. Any mapping corrections are made in the mapping document and validated in Sandbox before touching production data.

Owner reconciliation and User provisioning

We extract every distinct AddressTwo owner referenced on Contacts, Deals, and Activities and match by email against the Salesforce destination org's User table. Any owner without a matching Salesforce User is placed in a reconciliation queue. The customer's Salesforce admin provisions the missing Users (active or inactive depending on whether the original AddressTwo user is still active) before production migration begins. OwnerId references are required on standard objects so this step gates the production import.

Production migration in dependency order

We run production migration in record-dependency order: Account creation first (from extracted company names), then Contacts with AccountId resolved, then Opportunities with AccountId, OwnerId, and RecordTypeId resolved, then Activity history via Bulk API 2.0 for large volumes. Each phase emits a row-count reconciliation report before the next phase begins. We pause migration and notify the customer if any phase's reconciliation falls below 95 percent of expected records.

Cutover, validation, and automation handoff

We coordinate a write-freeze window on AddressTwo during final cutover, run a delta migration of any records created or modified since the initial export, then hand off to the customer to set Salesforce as the system of record. We deliver a written inventory of any AddressTwo reminder sequences or follow-up automation rules that require rebuilding in Salesforce Flow, with a recommended Flow equivalent for each. We support a one-week hypercare window to resolve any data quality issues raised by the customer's team during initial Salesforce use.