CRM migration
Field-level mapping, validation, and rollback between Agent Legend and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Agent Legend
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between Agent Legend and Nutshell.
Complexity
BStandard
Timeline
24–48 hours
Overview
Teams move from Agent Legend to Nutshell when their per-contact pricing model becomes unpredictable as the database grows, or when they want built-in email marketing without paying for a separate platform. Agent Legend's unified Contact model — which rolls leads, prospects, and customers into a single object with status tracking — splits into Nutshell's separate People, Company, and Lead objects during migration. FlitStack AI maps all data objects, preserves custom properties like Lily predictive scores and campaign tags, and surfaces automation logic as a rebuild reference so your team can reconstruct drip sequences in Nutshell's Sales Email module. The migration runs via scoped read access on Agent Legend, a test migration with field-level diff, then a full run with 24–48 hour delta pickup for any in-flight changes during cutover. Workflows, automations, and campaign logic do not migrate — those require a manual rebuild in Nutshell tools. During discovery, teams receive a complete field-level mapping specification and a custom field creation plan so the Nutshell schema is ready before any data moves. The migration does not require Agent Legend downtime; users continue working in the source system throughout the process.
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 Agent Legend 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.
Agent Legend
Contact
Nutshell
People
1:1Agent Legend Contact maps directly to Nutshell People for all active contacts. The Contact's status field (prospect, active, past client) is preserved as a custom pick-list field (Original_Status__c) on the People record. Status values route records to Nutshell People rather than Leads when status indicates a customer relationship.
Agent Legend
Contact (prospect status)
Nutshell
Lead
1:manyAgent Legend Contacts with status = 'prospect' or 'lead' split into Nutshell Leads rather than People. This preserves the top-of-funnel classification and keeps the sales pipeline clean. The original Contact status is captured in Original_Status__c for reporting continuity. This split is based on the source status field value during migration.
Agent Legend
Company
Nutshell
Company
1:1Agent Legend stores company data as contact properties (not a separate object). When a Contact has a company association, a Company record is created in Nutshell and linked via the People record's Company field. Nutshell's Company object stores name, domain, address, industry, employee count, and revenue. Parent-child company relationships in Agent Legend map to Nutshell's parent Company field.
Agent Legend
Deal
Nutshell
Opportunity
1:1Agent Legend Deal maps to Nutshell Opportunity. The Opportunity stores deal name, value, pipeline stage (Milestone), close date, and owner. Nutshell's pipeline model uses Milestones to represent stages within a pipeline — the Agent Legend deal stage name maps to the corresponding Milestone name in Nutshell's configured pipeline.
Agent Legend
Pipeline
Nutshell
Pipeline + Milestones
1:1Agent Legend's pipeline concept maps to Nutshell's Pipeline and Milestone model. Each Agent Legend pipeline becomes a Nutshell Pipeline, and each pipeline stage within it becomes a Milestone within that Pipeline. The Milestone names, order, and probabilities are mapped value-by-value from Agent Legend stage definitions. If Nutshell's pipeline is not pre-configured, FlitStack AI delivers a Milestone mapping plan before migration.
Agent Legend
Campaign
Nutshell
Activity / Custom Fields (no equivalent)
1:1Agent Legend Campaign contains drip sequences, conditional branching, timing rules, and campaign-level settings that cannot be stored as a single data field in Nutshell. Campaign names, types, and key configuration values are preserved as a custom text field (Original_Campaign__c) on the People record. The sequence logic, conditional rules, and automation steps must be rebuilt manually in Nutshell's Sales Email sequences and workflow automation tools.
Agent Legend
Engagement (Call, Email, Meeting, Note)
Nutshell
Activity
1:1Agent Legend engagement logs — calls, emails, meetings, and notes — map to Nutshell Activities. The activity type (Call, Email, Meeting, Note) is stored in Nutshell's Activity Type field. Original subject, body content, engagement date, and owner are preserved. Activities are linked to the corresponding People record in Nutshell by email-matched owner.
Agent Legend
Custom Property (scoring, tags, source)
Nutshell
People Custom Fields
1:1Agent Legend custom properties — including Lily predictive lead scores, lead sources, tags, and custom text/number fields — are mapped to Nutshell People Custom Fields. Nutshell supports custom fields for People, Company, and Lead objects. Number-type properties (scores) become Nutshell Number fields; text properties become Text or Long Text fields; pick-list values become Choice fields. The original custom property name is preserved in the Nutshell field label.
Agent Legend
Attachment / File
Nutshell
People Attachments / Company Attachments
1:1Agent Legend file attachments associated with contacts are migrated as file records attached to the corresponding People or Company record in Nutshell. File size limits and inline image handling are applied per Nutshell's attachment constraints. The original file name and upload date are preserved in the Nutshell attachment record.
Agent Legend
Owner / User
Nutshell
User
1:1Agent Legend owner assignments are resolved by matching the owner's email address to a Nutshell User. Unmatched owners are flagged before migration — the team either creates Nutshell user accounts first or assigns records to a designated fallback user. No record lands in Nutshell without a valid owner reference.
| Agent Legend | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | People1:1 | Fully supported | |
| Contact (prospect status) | Lead1:many | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline | Pipeline + Milestones1:1 | Fully supported | |
| Campaign | Activity / Custom Fields (no equivalent)1:1 | Fully supported | |
| Engagement (Call, Email, Meeting, Note) | Activity1:1 | Fully supported | |
| Custom Property (scoring, tags, source) | People Custom Fields1:1 | Fully supported | |
| Attachment / File | People Attachments / Company Attachments1:1 | Fully supported | |
| Owner / User | User1: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.
Agent Legend gotchas
Lily AI scores do not export from Agent Legend
CRM integration tokens and OAuth connections do not transfer
Contact-level per-message pricing creates billing risk on high-volume imports
Custom fields are not fully documented in the public API
Letter templates use proprietary merge tag syntax
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
Audit Agent Legend data and build the migration specification
FlitStack AI connects to Agent Legend via scoped read access and audits all records — contacts, companies, deals, engagement history, and custom properties including Lily scores and campaign tags. We produce a migration specification that maps every Agent Legend field to its Nutshell equivalent, flags custom properties that require Nutshell custom field creation, identifies contacts that route to Nutshell People versus Leads based on status, and documents the company-extraction logic. The specification is reviewed with your team before any data moves.
Create Nutshell custom fields and pipeline Milestones
Based on the migration specification, your Nutshell admin (or our team) creates the custom fields needed on People, Company, and Lead objects — including Lily_Score__c, Original_Status__c, Original_Source__c, Original_Campaign__c, and Source_System_ID__c. If Nutshell pipelines and Milestones are not pre-configured, FlitStack AI delivers a Milestone mapping plan specifying which Agent Legend pipeline stages map to which Nutshell Milestones so the pipeline can be configured before migration.
Resolve owners and run test migration with field-level diff
Agent Legend owner email addresses are matched to Nutshell Users. Any unmatched owners are flagged — your team creates Nutshell user accounts or designates a fallback owner before the full run. A representative test migration runs first, typically covering 100–500 records across contacts, companies, deals, and activities. FlitStack AI generates a field-level diff between the Agent Legend source and Nutshell destination so you can verify Lily score mapping, status routing, and company linking before the full migration commits.
Execute full migration with delta pickup and rollback
The full data migration runs against Nutshell — all contacts, companies, deals, activities, and custom properties are written to their target Nutshell objects with original create timestamps and owner assignments preserved. A delta-pickup window (typically 24–48 hours) captures any new or modified records created in Agent Legend during the cutover. FlitStack AI generates an audit log of every operation. If reconciliation fails, one-click rollback reverts Nutshell to its pre-migration state so the migration can be re-run with corrected mapping.
Platform deep dives
Agent Legend
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Agent Legend and Nutshell.
Object compatibility
1 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
Agent Legend: Not publicly documented.
Data volume sensitivity
Agent Legend 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 Agent Legend to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Agent Legend 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 Agent Legend
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.