CRM migration
Field-level mapping, validation, and rollback between Fulcrum Snap and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Fulcrum Snap
Source
Nutshell
Destination
Compatibility
10 of 11
objects map 1:1 between Fulcrum Snap and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Fulcrum Snap runs on SAP and manages every layer of law-firm operations: matter inception, client records, time tracking, e-billing, conflicts checks, and financial reporting. Nutshell is a focused CRM that models People (contacts), Companies (accounts), Leads, and Deals (pipeline stages) with built-in email marketing and a JSON-RPC API. The two platforms share almost no object vocabulary, so every migration is a deliberate schema translation rather than a field rename. We map Fulcrum Snap clients to Nutshell People and Companies, matters to Deals with custom fields carrying matter number, responsible attorney, and practice area. Billable hours migrate as closed Activity records with original date, duration, and billing code preserved in custom fields. E-billing records (Ebilling Efficacy module) have no direct Nutshell equivalent — we surface them as reference notes attached to the related company or deal and flag them for manual reconciliation in Nutshell's billing add-ons. Custom fields on Fulcrum Snap objects (SAP extension fields) migrate as Nutshell custom fields on the corresponding record type. We use Fulcrum Snap's REST API and CSV export options for data extraction, cross-referenced for completeness, then load into Nutshell via the Nutshell JSON-RPC API. A 100-record sample migration with field-level diff runs first so you verify matter-to-deal mapping, client-to-people mapping, and time-entry preservation before the full cutover commits.
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 Fulcrum Snap 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.
Fulcrum Snap
Client
Nutshell
People + Company
many:1Fulcrum Snap clients (legal entities or individuals) map to both a Nutshell People record and a Nutshell Company record. Primary individual contacts become People with a related Company; corporate clients create a Company record with the primary contact as a linked People record. The Fulcrum Snap client type field (individual vs. organization) drives whether the Nutshell record lands as People-first or Company-first.
Fulcrum Snap
Matter
Nutshell
Deal
1:1Fulcrum Snap matters have no direct Nutshell equivalent. We create a Nutshell Deal for each matter, using the matter name as the Deal name and the matter number stored in a custom field (Matter_Number__c). The responsible attorney maps to the Deal owner via email match against Nutshell users. Matter status (Active, Closed, On Hold) maps to Nutshell pipeline stage values defined per record type.
Fulcrum Snap
Matter Status
Nutshell
Deal Stage
1:1Fulcrum Snap matter lifecycle statuses (New, In Progress, Pending, Closed, Archived) are mapped value-by-value to Nutshell pipeline stage names. The mapping plan is delivered before migration runs so your admin can configure Nutshell pipeline stages to match the source statuses before data lands.
Fulcrum Snap
Time Entry
Nutshell
Activity (Task)
1:1Fulcrum Snap time entries map to Nutshell Activity records (Task type) linked to the corresponding Deal (matter). Original date, duration in minutes, billing code, and description are stored in custom fields on the Activity: Original_Date__c, Duration_Minutes__c, Billing_Code__c. Billable vs. non-billable flag migrates as a custom pick-list field.
Fulcrum Snap
Bill / E-Billing Record
Nutshell
Note attached to Company + Deal
1:1Fulcrum Snap's Ebilling Efficacy module produces invoices and LEDES 1998B exports with no Nutshell equivalent. Bill records are exported as Notes attached to the related Company and Deal, carrying invoice number, total amount, status (Sent, Paid, Overdue), and LEDES codes. Financial reconciliation must be completed in your accounting tool post-migration.
Fulcrum Snap
Custom Field (SAP Extension Field)
Nutshell
Custom Field on corresponding Nutshell record
1:1Fulcrum Snap extension fields on any object migrate as Nutshell custom fields on the matching record type. Field type translation is applied: SAP date fields become Nutshell date fields, pick-list values become Nutshell choice fields, currency fields become Nutshell number fields with two decimal precision. The mapping plan enumerates every custom field before migration runs.
Fulcrum Snap
Risk Assessment Record
Nutshell
Note on Company
1:1Fulcrum Snap's Risk Assessment module produces structured risk evaluations with severity scores and mitigation notes. These have no Nutshell equivalent. We export the full risk record as a rich-text Note attached to the related Company, preserving all risk data as reference text for post-migration review.
Fulcrum Snap
Conflict Check Result
Nutshell
Note on Company
1:1New Business Intake and Conflicts module results from Fulcrum Snap are captured as Notes on the relevant Company record. Conflict check status (Clear, Cleared with Notes, Conflict Found) and the responsible party are preserved. This is informational only — Nutshell does not enforce conflict checking natively.
Fulcrum Snap
Attachment / File
Nutshell
File attached to Nutshell record
1:1Fulcrum Snap file attachments on matters, clients, or time entries are downloaded and re-uploaded to the corresponding Nutshell record (Company, People, or Deal). File size limits from Nutshell apply (25MB per file). Inline images in Fulcrum Snap notes are extracted and rehosted as Nutshell file attachments.
Fulcrum Snap
User / Attorney
Nutshell
Nutshell User
1:1Fulcrum Snap user records are resolved against Nutshell users by email match. Unmatched attorneys are flagged before migration; your team either creates Nutshell user accounts first or assigns their records to a fallback owner. SAP role and permission sets do not transfer — Nutshell roles and permissions must be configured separately post-migration.
Fulcrum Snap
WIP (Work in Progress)
Nutshell
Note on Deal
1:1Fulcrum Snap WIP records track unbilled time against matters. WIP balances are preserved as Notes on the corresponding Nutshell Deal (matter) with original WIP amount, currency, and reporting date. Actual billing must be completed in your e-billing or accounting system post-migration.
| Fulcrum Snap | Nutshell | Compatibility | |
|---|---|---|---|
| Client | People + Companymany:1 | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Matter Status | Deal Stage1:1 | Fully supported | |
| Time Entry | Activity (Task)1:1 | Fully supported | |
| Bill / E-Billing Record | Note attached to Company + Deal1:1 | Fully supported | |
| Custom Field (SAP Extension Field) | Custom Field on corresponding Nutshell record1:1 | Fully supported | |
| Risk Assessment Record | Note on Company1:1 | Fully supported | |
| Conflict Check Result | Note on Company1:1 | Fully supported | |
| Attachment / File | File attached to Nutshell record1:1 | Fully supported | |
| User / Attorney | Nutshell User1:1 | Fully supported | |
| WIP (Work in Progress) | Note on Deal1:1 | Mapping required |
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.
Fulcrum Snap gotchas
SAP HANA schema complexity requires careful data mapping
Conflicts-denial flags block Matter recreation
Immutable time entries cannot be corrected post-sync on field app
Snap Insights dashboards are not migratable data
Custom fields schema must be extracted before migration
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
Map Fulcrum Snap modules to Nutshell record types and enumerate custom fields
We audit every active Fulcrum Snap module in your SAP deployment — core Snap, Ebilling Efficacy, TimeConnect, Risk Assessment, New Business Intake, and any custom SAP extension fields. For each module we identify the corresponding Nutshell record type (People, Company, Deal, Activity) and document every custom field that needs to be created in Nutshell before migration. A custom-field setup plan is delivered to your Nutshell admin with field names, types, and pick-list values to create. This step runs before any data is extracted so Nutshell's schema is ready when migration begins.
Extract data from Fulcrum Snap via API and CSV export, cross-reference for completeness
We extract data using Fulcrum Snap's REST API for real-time object reads and the CSV/PostgreSQL export tools for bulk record sets. Parallel exports run from both the Exporter and Downloader tools to capture all module data. Record counts are cross-referenced against Fulcrum Snap's internal reporting to identify any gaps — particularly in the e-billing, risk assessment, and custom field modules. Any discrepancies are resolved before mapping is finalized.
Match Fulcrum Snap users to Nutshell users by email and flag unresolved owners
Fulcrum Snap user accounts are matched against Nutshell users by email address. We generate a pre-migration ownership report listing every matched owner, every unmatched Fulcrum Snap user, and the record count affected by each. Your team creates Nutshell user accounts for any unmatched attorneys before the full migration runs. Records belonging to unresolved owners are assigned to a designated fallback Nutshell user with a note in the record for later reassignment.
Run a sample migration of 100–200 records with field-level diff
A representative sample migration runs first — spanning clients, matters, time entries, e-billing records, and custom-field-populated deals. We generate a field-level diff between the source Fulcrum Snap records and the destination Nutshell records so you can verify that matter-to-deal mapping, client-to-people mapping, time-entry date preservation, and custom field population all meet expectations. Sample results are reviewed with you before the full migration is scheduled.
Execute full migration with delta-pickup window and one-click rollback
The full migration runs against Nutshell's JSON-RPC API. A delta-pickup window of 24–48 hours captures any records created or modified in Fulcrum Snap during the cutover. All operations are logged to an audit trail so you can trace every migrated record back to its source. If reconciliation fails — record counts don't match, custom fields are missing, or deal relationships are broken — one-click rollback reverts the Nutshell target to its pre-migration state. You continue working in Fulcrum Snap throughout the window.
Post-migration validation and billing workflow handoff
We run a post-migration validation comparing source record counts per Fulcrum Snap module against destination record counts in Nutshell. Custom fields are spot-checked for data accuracy. A handoff document summarizes the migrated record volumes, any notes or reference records created for e-billing and WIP, and the list of Nutshell custom fields that need your team to configure roles and permissions. Nutshell billing integrations (QuickBooks, Stripe) are configured separately as a post-migration step.
Platform deep dives
Fulcrum Snap
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 Fulcrum Snap 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
Fulcrum Snap: Rate limits are documented in Fulcrum's Acceptable Use Policy and enforced per-org by the operations team; specific per-minute thresholds are not publicly disclosed.
Data volume sensitivity
Fulcrum Snap 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 Fulcrum Snap to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Fulcrum Snap 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 Fulcrum Snap
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.