CRM migration
Field-level mapping, validation, and rollback between AddressTwo and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
AddressTwo
Source
Nutshell
Destination
Compatibility
7 of 10
objects map 1:1 between AddressTwo and Nutshell.
Complexity
BStandard
Timeline
1-2 weeks
Overview
Moving from AddressTwo to Nutshell is a data-model normalization plus a pricing-structure transition. AddressTwo stores company information as a field on the Contact record; Nutshell maintains Companies and People as separate objects with a link between them. We flatten AddressTwo's company-on-contact data into a Nutshell Company record, then link each Person to it via the accountId lookup. BCC-collected email history migrates as a flattened conversation log. AddressTwo's built-in mass-email campaigns migrate as a contact-list record, with campaign membership preserved and analytics flags cleared for rebuild in Nutshell's Engagement suite. Workflows, reminders, and follow-up automation do not migrate; we deliver a written inventory for the customer to rebuild inside Nutshell. The pricing shift from AddressTwo's flat $14.95/month to Nutshell's per-user model (starting at $13/user/month annually) is the most significant cost-impact item for multi-user accounts and is flagged during scoping.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a AddressTwo object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
AddressTwo
Contact
Nutshell
Person
1:1AddressTwo Contacts map 1:1 to Nutshell People. Every standard contact field (name, email, phone, address) migrates directly. The AddressTwo contact's associated company name is held during import and used to resolve the accountId lookup into the Nutshell Company record created from the same data.
AddressTwo
Company (flattened on Contact)
Nutshell
Company
1:manyAddressTwo does not store Companies as a separate object — company name is a field on the Contact record. We extract all distinct company names during extraction, deduplicate them, create a Nutshell Company record for each unique name, and link all associated People records to it via accountId. This reconstructs the one-to-many relationship that AddressTwo does not natively model.
AddressTwo
Deal
Nutshell
Opportunity
1:1AddressTwo Deals map to Nutshell Opportunities. Stage name, deal value, owner assignment, and order status migrate directly. We map the AddressTwo pipeline to a Nutshell pipeline configuration, and the deal stage maps to the corresponding Nutshell stage. Closed-won and closed-lost states preserve their original reason if stored as a custom field.
AddressTwo
Activity
Nutshell
Task
1:1AddressTwo Activities (calls, meetings, emails, tasks) are date-stamped events tied to a Contact. We migrate each activity as a Nutshell Task with the activity type preserved in a custom field, the original timestamp set as the task due date, and the owner resolved via email match against Nutshell Users.
AddressTwo
Note
Nutshell
Note
1:1Free-text notes attached to an AddressTwo Contact migrate as-is into Nutshell Notes linked to the corresponding Person record. Notes carry no structured fields so they transfer verbatim with their original creation timestamp preserved.
AddressTwo
Email History
Nutshell
Note
1:1AddressTwo stores email threads collected by BCC into a flattened conversation log per Contact. We import this as a Nutshell Note on the Person record with a header indicating it originated from BCC email history. Individual email metadata (sender, recipient, timestamp) is preserved within the note body as exported.
AddressTwo
Tag
Nutshell
Tag
1:1AddressTwo contact tags migrate as a flat array to Nutshell Tags on the Person record. Nutshell supports tagging People and Companies for segmentation. Tag names transfer verbatim; any tag longer than Nutshell's limit is truncated with an audit log entry.
AddressTwo
Mass Email Campaign
Nutshell
People List
1:1AddressTwo campaign membership — which contacts were included in a mass email send — migrates as a Nutshell People List with the campaign name preserved. Open rates, click rates, and send analytics do not export from AddressTwo and are noted as items to rebuild inside Nutshell Engagement using campaign export data if available.
AddressTwo
Custom Field (Contact)
Nutshell
Custom Field (Person)
lossyAddressTwo custom fields on Contacts map to Nutshell custom fields on People. We match by field name and type, creating any missing Nutshell custom fields before import. Date, currency, text, and checkbox types map directly; unsupported types are flagged for customer review.
AddressTwo
Custom Field (Deal)
Nutshell
Custom Field (Opportunity)
lossyAddressTwo custom fields on Deals map to Nutshell custom fields on Opportunities using the same name-and-type matching logic. Pipeline-specific custom fields are created under the Opportunity object scope before migration begins.
| AddressTwo | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company (flattened on Contact) | Company1:many | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Activity | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Email History | Note1:1 | Mapping required | |
| Tag | Tag1:1 | Fully supported | |
| Mass Email Campaign | People List1:1 | Fully supported | |
| Custom Field (Contact) | Custom Field (Person)lossy | Fully supported | |
| Custom Field (Deal) | Custom Field (Opportunity)lossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
AddressTwo gotchas
API requires approved key obtained via email to support
No self-service data export or bulk download
Duplicate contact creation during email sync
QuickBooks integration does not exist
No formally documented API rate limits
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Data extraction and scoping
We initiate contact with AddressTwo support to request an API key and a full account export including Contacts, Deals, Activities, Notes, and campaign membership. While awaiting approval, we use the CSV export path (requested via support ticket) as a parallel fallback. We audit the exported data for record counts, custom field definitions, pipeline stage names, activity volume, and tag vocabulary. We also confirm the address-two company's per-user pricing tiers and whether the customer plans to use Nutshell's Engagement suite (for email campaign rebuild scope) or only the CRM layer.
Schema pre-creation in Nutshell
Before any data loads, we create any missing Nutshell custom fields on Person and Opportunity to match AddressTwo custom field names and types. We configure the Nutshell pipeline to match AddressTwo's stage names, setting stage probabilities to match the original deal values. If the customer uses multiple pipelines in AddressTwo, we replicate each as a separate Nutshell pipeline. Tags are preserved as-is; no pre-creation is needed since Nutshell creates tags dynamically on import.
Company reconstruction and Person import
We extract all distinct company names from the AddressTwo Contact export, deduplicate them, and insert them as Nutshell Company records first. Then we import all AddressTwo Contacts as Nutshell People, resolving each Person's accountId to the corresponding Company record via a lookup table built during the company extraction phase. We run a de-duplication pass on email addresses before import to catch any duplicate Contacts that arose from AddressTwo's BCC sync behavior. Owner email matches against the Nutshell User table; unresolved owners are flagged for the customer admin.
Opportunity import with pipeline mapping
We import AddressTwo Deals as Nutshell Opportunities using the stage and pipeline mapping configured in step two. Each Opportunity is linked to the Account (reconstructed Company) and the resolved Owner. Closed-won and closed-lost values preserve their original deal amount and close date. Any custom fields on AddressTwo Deals map to the pre-created Nutshell custom fields on Opportunity. We emit a row-count reconciliation report comparing AddressTwo Deal count to Nutshell Opportunity count before declaring this phase complete.
Activity history and notes import
We import AddressTwo Activities as Nutshell Tasks, preserving the original timestamp as the due date, the activity type in a custom field, and the owner via email lookup. Notes migrate as Nutshell Notes linked to the Person record. BCC email thread content migrates as a single Note per Contact with a header identifying it as BCC email history. Campaign membership migrates as Nutshell People Lists, with each campaign member resolved to the migrated Person record.
Cutover, validation, and automation inventory delivery
We freeze AddressTwo writes during the cutover window and run a delta migration of any records modified since the initial extract. We deliver a row-count validation report comparing source and destination record totals across Contacts/People, Companies/Accounts, Deals/Opportunities, and Activities/Tasks. We deliver a written automation inventory listing every AddressTwo workflow, reminder, and follow-up sequence with a rebuild recommendation for Nutshell. We support a 72-hour post-cutover window for data quality issues; we do not rebuild automations inside Nutshell as standard scope.
Platform deep dives
AddressTwo
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across AddressTwo and Nutshell.
Object compatibility
3 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
AddressTwo: Not publicly documented.
Data volume sensitivity
AddressTwo doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during AddressTwo to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your AddressTwo to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave AddressTwo
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.