CRM migration
Field-level mapping, validation, and rollback between eTrigue and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
eTrigue
Source
Nutshell
Destination
Compatibility
5 of 8
objects map 1:1 between eTrigue and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
Moving from eTrigue DemandCenter to Nutshell is a migration from a campaign-centric marketing automation tool into a full CRM with deal and account management. eTrigue organizes data around Prospects and Campaigns with no native Deals, Accounts, or Opportunities; Nutshell uses Contacts, Organizations (Accounts), Leads, and Deals as first-class objects. We extract via eTrigue's built-in CSV export tool, decode the numeric Status field codes (1 = Active, 2 = Opt-Out), map each of the five Lead Score sub-components to individual custom fields on the Nutshell Contact, and load into Nutshell via the REST API. We do not migrate Landing Pages, Progressive Forms, or partner channel program structures as functional assets; we deliver a written field-level inventory for manual rebuild. Workflows and automations in eTrigue do not have a Nutshell equivalent and are outside migration scope.
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 eTrigue 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.
eTrigue
Prospect
Nutshell
Contact
1:1eTrigue Prospects map 1:1 to Nutshell Contacts. Standard fields (name, email, company, phone) export cleanly from the Prospects list CSV and load into the Contact object via Nutshell API. First name and last name are split from the full Prospect name during the transform phase. The prospect's Organization is resolved by matching the exported company field against Nutshell Organizations, creating the Organization if it does not exist, and linking Contact to it via the primary_organization_id field.
eTrigue
Prospect Status field
Nutshell
Contact email_opt_in flag
lossyeTrigue exports the Status field as numeric codes (e.g., 1 = Active, 2 = Opt-Out) rather than human-readable labels. We decode these codes during data profiling before any import. Active prospects map to email_opt_in = true; Opt-Out and other codes map to email_opt_in = false. Without this decoding step, all records import as active, silently unsubscribing no one.
eTrigue
Lead Score sub-components
Nutshell
Contact custom numeric fields
lossyeTrigue stores five separate Lead Score sub-components as numeric fields on the Prospect: Campaign Score, Activity Score, Source Score, Relationship Score, and Buy Time Score. Nutshell has no native equivalent scoring model. We create five custom numeric fields on the Contact object (campaign_score__c, activity_score__c, source_score__c, relationship_score__c, buytime_score__c) before import and load each sub-score individually. The composite total can be reconstructed as a formula field or used by the customer's scoring logic post-migration.
eTrigue
3D Lead Scoring composite value
Nutshell
Contact custom numeric field
1:1eTrigue's 3D Lead Scoring model enriches the standard 5-component score with content-type engagement weighting. We export the composite 3D score as a single numeric value and store it in a custom field (score_3d__c) on the Nutshell Contact. This preserves the enriched scoring signal for customers who used 3D scoring to rank prospect quality. Destination scoring logic is the customer's responsibility post-migration.
eTrigue
Campaign
Nutshell
Campaign
1:1eTrigue Campaigns map to Nutshell Campaigns. Campaign name, start date, and campaign type migrate. Email send history and response data (opens, clicks, bounces) from eTrigue's campaign reporting exports are loaded into Nutshell Campaign Members and campaign activity notes. Nutshell Campaigns track mailing lists and email sends rather than automated nurture journeys, so the campaign response timeline is preserved but the workflow logic is not.
eTrigue
Activity History
Nutshell
Activity (Task)
1:1eTrigue records page views, email opens, form submissions, and campaign responses with timestamps on the Prospect's Activity History tab. We export this as a structured activity log and map it to Nutshell Activities (Task records) linked to the Contact. Each activity type is tagged by category (page_view, email_open, form_submission, campaign_response) in the activity_notes field so the timeline is readable in Nutshell. Activity timestamps are preserved as the Task due date and creation date.
eTrigue
Custom Fields (Boolean, Text, Number)
Nutshell
Contact custom fields
lossyeTrigue supports Boolean, Text, Number, and other custom field types under Settings > Prospect Settings > Prospect Fields. We create matching custom fields on the Nutshell Contact object before import. Boolean fields with custom labels (e.g., 'Has Demo Scheduled: Yes / No') map to Nutshell Boolean custom fields. Text fields map to String custom fields. Number fields map to Numeric custom fields. All field definitions and label mappings are documented in the field inventory delivered before import.
eTrigue
Partner/Channel Program data
Nutshell
Organization or Contact custom field
1:1eTrigue Lead Accelerator customers store partner organization names and campaign attribution in custom Prospect fields rather than a native Partner object. We map these to either the Nutshell Organization (if the partner organization is the primary account) or a custom Contact field (partner_name__c or partner_campaign__c) depending on the customer's data model. Partner-specific scoring rules that exist in eTrigue are documented for manual recreation in Nutshell rules post-migration.
| eTrigue | Nutshell | Compatibility | |
|---|---|---|---|
| Prospect | Contact1:1 | Fully supported | |
| Prospect Status field | Contact email_opt_in flaglossy | Fully supported | |
| Lead Score sub-components | Contact custom numeric fieldslossy | Fully supported | |
| 3D Lead Scoring composite value | Contact custom numeric field1:1 | Fully supported | |
| Campaign | Campaign1:1 | Fully supported | |
| Activity History | Activity (Task)1:1 | Fully supported | |
| Custom Fields (Boolean, Text, Number) | Contact custom fieldslossy | Fully supported | |
| Partner/Channel Program data | Organization or Contact custom field1:1 | 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.
eTrigue gotchas
No public API means migration relies on CSV export only
Opt-Out status encoding in Status field export
Lead Score sub-components are five separate fields, not one
Partner program data stored in custom fields, not a native object
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
Discovery and CSV export assembly
We audit the eTrigue portal for prospect volume, active campaign count, custom field definitions, 3D Lead Scoring configuration, and any partner program custom fields. We identify the CSV export batches required to capture all Prospects and Activity History using saved search filters, since the lack of a public API requires manual export coordination with the customer. The discovery output is a written migration scope with a full field inventory listing every source field, its type, and its proposed Nutshell destination.
Status code decoding and data profiling
We run a data profiling pass on the exported CSV before any import. This step decodes the numeric Status field values to their human-readable equivalents and flags any records with non-standard status codes that require manual review. We also profile email deliverability fields (bounce flags, unsubscribe flags) to ensure they map correctly to Nutshell's email_opt_in behavior. The profiling output is a data quality report shared with the customer for approval before import begins.
Nutshell schema configuration
We create the custom Contact fields in Nutshell before any data import. This includes five numeric fields for the Lead Score sub-components (campaign_score__c, activity_score__c, source_score__c, relationship_score__c, buytime_score__c), a custom field for the 3D composite score (score_3d__c), a Boolean field for any Boolean custom fields from eTrigue, and any partner attribution fields (partner_name__c, partner_campaign__c). We use the Nutshell API to create fields. The customer approves the field configuration before record migration begins.
Organization and Contact import
We import records in dependency order. First, we extract unique Organization names from the exported Prospect company field and create Nutshell Organizations for each. Then we import Contacts with the Organization relationship resolved via the primary_organization_id field. The five Lead Score sub-components load into the corresponding custom numeric fields. The 3D composite score loads into score_3d__c. Status codes decode to email_opt_in during this phase. Each import batch emits a reconciliation count (records in, records created, records updated, records rejected) before the next phase begins.
Campaign and Activity History migration
We import eTrigue Campaigns into Nutshell Campaigns, then load the Activity History from the Prospect export as Nutshell Activity records (Tasks) linked to the corresponding Contact. Activity type (page_view, email_open, form_submission, campaign_response) is stored in the activity notes field. Timestamps are preserved as the Task due date. For customers with large activity histories, we batch the activity import to avoid API rate limit responses from Nutshell and use exponential backoff on any 429 responses.
Cutover, validation, and rebuild handoff
We freeze writes in eTrigue during the cutover window and run a final delta migration of any records modified during the migration window. We validate by reconciling record counts (Contacts imported vs. Prospects exported, Activities imported vs. Activity History rows exported) and spot-checking 20-30 records against the source export. We deliver the field inventory, Status code mapping reference, and a written note of any eTrigue automations and landing pages that require manual rebuild in the customer's chosen tools. We do not rebuild automations or forms inside the migration scope.
Platform deep dives
eTrigue
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 eTrigue and Nutshell.
Object compatibility
2 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
eTrigue: Not publicly documented.
Data volume sensitivity
eTrigue 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 eTrigue to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your eTrigue 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 eTrigue
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.