CRM migration

Migrate from Agent Legend to Nutshell

Field-level mapping, validation, and rollback between Agent Legend and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Agent Legend logo

Agent Legend

Source

Nutshell

Destination

Nutshell logo

Compatibility

90%

9 of 10

objects map 1:1 between Agent Legend and Nutshell.

Complexity

BStandard

Timeline

24–48 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Agent Legend logo

Agent Legend

What's pushing teams away

  • The per-contact pricing model ($0.40/contact) becomes expensive at scale as contact databases grow into the thousands, with no flat-rate unlimited tier available.
  • Lily AI features (lead scoring, data enrichment) are proprietary and do not export with contact records, meaning migration means losing the intelligence layer built over years.
  • Steep learning curve around campaign setup, Circle Prospecting configuration, and CRM integration workflows frustrates agents who expect faster time-to-value.
  • Limited multi-user collaboration features on lower tiers, with seat-based pricing creating friction for teams that need shared inbox or role-based access controls.
  • Customer support responsiveness is inconsistent, with some users reporting delayed responses when integration or billing issues arise.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Agent Legend objects map to Nutshell

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

maps to

Nutshell

People

1:1
Fully supported

Agent 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)

maps to

Nutshell

Lead

1:many
Fully supported

Agent 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

maps to

Nutshell

Company

1:1
Fully supported

Agent 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

maps to

Nutshell

Opportunity

1:1
Fully supported

Agent 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

maps to

Nutshell

Pipeline + Milestones

1:1
Fully supported

Agent 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

maps to

Nutshell

Activity / Custom Fields (no equivalent)

1:1
Fully supported

Agent 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)

maps to

Nutshell

Activity

1:1
Fully supported

Agent 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)

maps to

Nutshell

People Custom Fields

1:1
Fully supported

Agent 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

maps to

Nutshell

People Attachments / Company Attachments

1:1
Fully supported

Agent 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

maps to

Nutshell

User

1:1
Fully supported

Agent 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.

Gotchas + challenges

What specifically takes care here

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 logo

Agent Legend gotchas

High

Lily AI scores do not export from Agent Legend

High

CRM integration tokens and OAuth connections do not transfer

Medium

Contact-level per-message pricing creates billing risk on high-volume imports

Medium

Custom fields are not fully documented in the public API

Low

Letter templates use proprietary merge tag syntax

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • Active Contact billing model has no Nutshell equivalent

    Agent Legend bills per active contact — a contact who receives at least one automated message per billing month. Storing contacts is free, but crossing the active-contact threshold triggers tier-based charges that scale with outreach volume. Nutshell charges per user seat with unlimited contacts regardless of outreach frequency. This fundamental billing model difference means the cost comparison cannot be made field-by-field. We preserve the active-contact flag as a custom field on each People record (Marketing_Contact_in_Source__c) so the finance team can rebuild the cost model in Nutshell's billing dashboard.

  • Lily AI lead scoring and Circle Prospecting require manual rebuild in Nutshell

    Agent Legend's Lily module runs predictive lead scoring across 1,600+ third-party data points to surface the 5–10% of a database most likely to transact. Circle Prospecting automates geo-targeted outreach sequences. Nutshell has no native equivalent to either feature — Nutshell IQ provides basic contact intelligence but not predictive scoring. We migrate Lily scores as a custom number field (Lily_Score__c) so historical prioritization is visible in Nutshell reports, but the scoring model and Circle Prospecting logic must be rebuilt manually using Nutshell's workflow automation builder and Sales Email sequences.

  • Contact-to-Company model divergence requires Contact-type routing

    Agent Legend stores company data as properties on the Contact record — there is no separate Company object in Agent Legend's standard schema. Nutshell separates People and Companies into distinct objects with a many-to-one relationship (one Person can belong to one primary Company). During migration, company data is extracted from Agent Legend Contact properties, a Company record is created in Nutshell for each unique company name, and the People record is linked to that Company. Agent Legend contacts without a company association land as standalone People records with no Company link.

  • Agent Legend API limits contact activity history to 90-day window

    Agent Legend's API provides engagement and activity history on a rolling 90-day basis. Older activity records — call logs, email threads, meeting notes beyond 90 days — may not be accessible via API export and therefore cannot be migrated automatically. We document this boundary during the discovery audit and recommend that teams with compliance or regulatory requirements for long-term activity history export manually before the migration window. All activity within the 90-day window migrates fully with original timestamps and owner assignments.

  • Campaign drip sequences and automation logic do not map to Nutshell fields

    Agent Legend Campaign objects contain drip sequences, conditional branching rules, timing delays, and Circle Prospecting trigger settings that are configuration data, not record fields. These cannot be represented as a single data value in Nutshell's schema. We export the campaign name, type, and key configuration values as a custom text field on the People record (Original_Campaign__c) for reference. The drip sequence logic, conditional rules, and automation triggers must be rebuilt in Nutshell's Sales Email sequence builder and workflow automation tools — a task we support with a campaign-definition export document.

Migration approach

Six steps for a successful Agent Legend to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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

Context on both ends of the pair

Agent Legend logo

Agent Legend

Source

Strengths

  • Lily AI lead scoring provides actionable prioritization without requiring technical setup or third-party data pipelines.
  • Circle Prospecting automates recurring geographic outreach, saving agents an estimated 19.7 hours per month on manual database sorting.
  • Native integrations with Follow Up Boss, Lofty, and 500+ lead sources reduce duplicate data entry across the real estate agent stack.
  • Predictable per-contact pricing with annual billing option that waives the $499 setup fee for qualifying teams.
  • Campaign response rates of 28–55% significantly exceed industry averages of 2–6%, validating the AI-driven targeting approach.

Weaknesses

  • Per-contact pricing scales poorly at high volume with no unlimited tier, making the platform expensive for large databases.
  • AI intelligence (Lily scores, enrichment data) does not export, meaning years of lead prioritization data are lost on migration.
  • Limited public API documentation and unclear rate limiting create challenges for custom automation and migration tooling.
  • Single-seat Starter tier restricts team collaboration, pushing teams toward higher tiers for shared access.
  • Customer support responsiveness is inconsistent according to third-party reviews, which complicates issue resolution during migration.
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Agent Legend and Nutshell.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Agent Legend: Not publicly documented.

  • Data volume sensitivity

    B

    Agent Legend doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Agent Legend to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Agent Legend to Nutshell data migrations

Answers to the questions buyers ask most during Agent Legend to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most Agent Legend to Nutshell migrations complete within 24–48 hours of clock time for setups under 50,000 records. Larger databases with 200,000+ records, complex custom property schemas, or extensive engagement history extend to 5–7 days. The longest planning step is creating Nutshell custom fields and configuring pipeline Milestones before data lands — FlitStack AI delivers that plan during the discovery audit so the destination schema is ready before migration runs.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Agent Legend.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day