CRM migration
Field-level mapping, validation, and rollback between Captorra and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Captorra
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Captorra and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Captorra and Nutshell serve different primary use cases: Captorra is an intake and case-management platform built for plaintiff-side law firms, with a data model organized around lead intake, referral tracking, and matter status. Nutshell is a sales CRM that structures data around People, Companies, Leads, and Deals with a visual pipeline and built-in email marketing. The migration maps Captorra's contact and company records directly to Nutshell's People and Companies objects, converts Captorra intake cases into Nutshell Deals (with your chosen pipeline stages), and surfaces custom intake fields as Nutshell custom fields on the matching objects. Captorra's legal-specific automations — intake routing, status-change triggers, and referral workflows — do not migrate; they require rebuilding in Nutshell's workflow tools or exported as reference documents for your admin. Activity history (notes, tasks, completed activities) transfers with original timestamps and owner links preserved. Owner resolution runs against Nutshell user email addresses — unmatched owners are flagged for manual assignment before the full run commits. The migration uses scoped read access to Captorra's API during the extraction phase so your team continues working uninterrupted.
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 Captorra 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.
Captorra
Person / Contact
Nutshell
Person
1:1Captorra person records (intake contacts) map directly to Nutshell People. Fields including name, email, phone, and address transfer 1:1. Original create date is preserved as a custom datetime field since Nutshell sets CreatedDate at import time. The custom field (Original_Create_Date__c) captures the exact original creation timestamp for historical reporting and sorting by record age.
Captorra
Intake Lead
Nutshell
Lead
1:1Captorra records that have not been converted to a matter map to Nutshell Leads. These include unqualified prospects captured through Captorra's intake form but not yet assigned to a case or attorney. The Lead captures the same contact fields plus intake-specific source attribution. Unconverted intake records retain their original intake form data for downstream follow-up.
Captorra
Company / Firm
Nutshell
Company
1:1Captorra companies (law firms, opposing counsel, referral sources) map to Nutshell Companies. Company name, address, website, and industry map directly. Captorra's custom firm-level fields surface as Nutshell Company custom fields. This ensures that firm-specific metadata like referral partner status or opposing counsel details are preserved in the new CRM environment.
Captorra
Intake / Matter
Nutshell
Deal
1:1Captorra's intake record or matter becomes a Nutshell Deal. The intake status (New, Assigned, Working, Pending, Closed) maps to a custom pick-list field on the deal, while the Nutshell pipeline stage represents the current sales or engagement phase — these are separate concepts and both are preserved. The dual-track status system maintains both legal matter lifecycle and sales pipeline visibility simultaneously.
Captorra
Intake Status Field
Nutshell
Custom Field (on Deal)
1:1Captorra's matter-status field (e.g., New, Assigned, Working, Pending, Closed) has no direct equivalent in Nutshell's standard deal fields. We create a custom pick-list field (Intake_Status__c) on the Deal object to preserve the original matter status for reference and reporting continuity. This field is informational only and does not control Nutshell's pipeline stages.
Captorra
Referral Source
Nutshell
Custom Field (on Person / Lead)
1:1Captorra tracks where each intake lead originated (partner referral, online form, advertising, etc.). This maps to a custom field on Nutshell Person or Lead (Referral_Source__c) as a pick-list or free-text field depending on the source value variety and your reporting needs. The field preserves lead attribution data that Captorra captured during the intake process.
Captorra
Activity / Note
Nutshell
Activity / Note
1:1Captorra notes and completed activity history (calls logged, tasks completed, emails associated with an intake) map to Nutshell Activities and Notes. Original timestamps, owners, and parent-record links are preserved so the engagement history carries over. This ensures your team can view the complete interaction timeline for each client or matter in Nutshell.
Captorra
Owner / Assigned Attorney
Nutshell
Owner (User)
1:1Captorra owner or assigned attorney resolves by email match against Nutshell Users. Unmatched owners are flagged before migration and assigned to a fallback owner — no record lands without a resolved owner. The email-based resolution ensures accurate ownership attribution when attorney email addresses exist in both systems.
Captorra
Custom Intake Fields
Nutshell
Custom Fields
1:1Any Captorra custom fields not covered by the standard mapping (e.g., Insurance_Provider__c, Accident_Type__c, Statute_of_Limitations__c) are created as Nutshell custom fields on the relevant object (Person, Company, or Deal) with matching field type — pick-list, text, date, number, or currency. Each field is validated against Nutshell's supported types before migration.
Captorra
ROI / Financial Fields
Nutshell
Custom Fields (on Deal)
1:1Captorra's ROI analytics fields (case value, expected settlement, contingency percentage) map to custom currency or number fields on the Nutshell Deal. These do not affect Nutshell's standard Amount field — they are additive for law-firm reporting needs. Financial metrics remain accessible for case evaluation and settlement tracking within the CRM environment.
| Captorra | Nutshell | Compatibility | |
|---|---|---|---|
| Person / Contact | Person1:1 | Fully supported | |
| Intake Lead | Lead1:1 | Fully supported | |
| Company / Firm | Company1:1 | Fully supported | |
| Intake / Matter | Deal1:1 | Fully supported | |
| Intake Status Field | Custom Field (on Deal)1:1 | Fully supported | |
| Referral Source | Custom Field (on Person / Lead)1:1 | Fully supported | |
| Activity / Note | Activity / Note1:1 | Fully supported | |
| Owner / Assigned Attorney | Owner (User)1:1 | Fully supported | |
| Custom Intake Fields | Custom Fields1:1 | Fully supported | |
| ROI / Financial Fields | Custom Fields (on Deal)1: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.
Captorra gotchas
Inbound-only API with no export endpoint
Custom field schema varies per organization
No public pricing or trial available
Intake form configurations do not auto-transfer
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
Inventory Captorra data and map to Nutshell schema
FlitStack AI connects to Captorra's API using scoped read credentials and inventories all person, company, lead, and intake records. We compare Captorra's custom field list against Nutshell's standard fields and flag gaps that require custom field creation. The result is a field-level mapping document that your admin reviews and approves before any data moves — this is where intake status, referral source, and legal-specific fields are assigned to their Nutshell equivalents.
Create Nutshell custom fields and configure pipeline stages
Before records load, FlitStack creates the custom fields identified in the mapping plan — Intake_Status__c, Referral_Source__c, Case_Value__c, and any other Captorra custom fields. Your admin configures the Nutshell pipeline stages that correspond to your firm's matter lifecycle (e.g., New Intake, Under Review, Active Case, Settlement, Closed). This ensures deals land in the correct pipeline bucket on day one. The pipeline configuration is validated against your Captorra matter-status distribution so no stage is inadvertently left empty after migration.
Resolve owners by email and flag unresolved accounts
Captorra owner and assigned-attorney records are matched against Nutshell Users by email address. Matches link the record to the correct Nutshell owner. Unmatched owners — records where the attorney or intake staff has no Nutshell account — are flagged and assigned to a fallback user you designate. No record migrates without a resolved owner; unresolved records are held in a staging group for manual assignment.
Run a sample migration with field-level diff
A representative slice of records — typically 100–300 spanning people, companies, leads, deals, and activity history — migrates first. FlitStack generates a field-level diff report comparing source values against Nutshell field values so you can verify intake-status mapping, referral-source field population, and deal pipeline assignment before the full run commits. Adjustments to the mapping plan are made before proceeding. The sample run also validates that custom field types (pick-list values, currency formatting, date formats) render correctly in Nutshell.
Execute full migration with delta-pickup cutover window
The full dataset migrates to Nutshell, following the sequenced order: Companies first, then People and Leads, then Deals with their linked contacts. A delta-pickup window (24–48 hours) captures any records created or modified in Captorra during the migration run so Nutshell reflects the final state at go-live. FlitStack generates an audit log of every record migrated, and one-click rollback is available if reconciliation reveals data integrity issues.
Platform deep dives
Captorra
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 Captorra 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
Captorra: Not publicly documented.
Data volume sensitivity
Captorra 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 Captorra to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Captorra 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 Captorra
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.