CRM migration

Migrate from Fulcrum Snap to Nutshell

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

Fulcrum Snap logo

Fulcrum Snap

Source

Nutshell

Destination

Nutshell logo

Compatibility

91%

10 of 11

objects map 1:1 between Fulcrum Snap and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Fulcrum Snap logo

Fulcrum Snap

What's pushing teams away

  • Steep learning curve for non-SAP users — attorneys and staff without SAP experience find the interface less intuitive than consumer-grade legal CRMs, with a 3-6 month ramp reported in user forums.
  • High total cost of ownership — licensing SAP, HANA infrastructure, and Fulcrum Snap together produces a cost structure that mid-sized firms find difficult to justify against simpler alternatives.
  • Customization constraints — while Snap is configurable, deep customizations that deviate from SAP's data model require developer-level changes and SAP consultant involvement.
  • Integration complexity with non-SAP systems — firms using practice-management tools outside the SAP ecosystem report that building integrations is time-consuming and often requires middleware.
  • Long implementation timelines — despite Fulcrum GT's fixed-scope marketing, firms report that aligning SAP configuration to firm-specific billing rules can extend past the initial project window.

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 Fulcrum Snap objects map to Nutshell

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

maps to

Nutshell

People + Company

many:1
Fully supported

Fulcrum 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

maps to

Nutshell

Deal

1:1
Fully supported

Fulcrum 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

maps to

Nutshell

Deal Stage

1:1
Fully supported

Fulcrum 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

maps to

Nutshell

Activity (Task)

1:1
Fully supported

Fulcrum 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

maps to

Nutshell

Note attached to Company + Deal

1:1
Fully supported

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

maps to

Nutshell

Custom Field on corresponding Nutshell record

1:1
Fully supported

Fulcrum 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

maps to

Nutshell

Note on Company

1:1
Fully supported

Fulcrum 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

maps to

Nutshell

Note on Company

1:1
Fully supported

New 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

maps to

Nutshell

File attached to Nutshell record

1:1
Fully supported

Fulcrum 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

maps to

Nutshell

Nutshell User

1:1
Fully supported

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

maps to

Nutshell

Note on Deal

1:1
Mapping required

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

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.

Fulcrum Snap logo

Fulcrum Snap gotchas

High

SAP HANA schema complexity requires careful data mapping

High

Conflicts-denial flags block Matter recreation

Medium

Immutable time entries cannot be corrected post-sync on field app

Medium

Snap Insights dashboards are not migratable data

Medium

Custom fields schema must be extracted before migration

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

  • Matters map to Deals with no native Nutshell equivalent — custom field scaffolding is required before migration

    Fulcrum Snap organizes all law-firm data around Matters: every client interaction, time entry, document, and billing record is hierarchically nested under a Matter. Nutshell's Deal object models sales pipeline stages for individual opportunities, not multi-month legal engagements with embedded time, billing, and risk data. Without pre-created custom fields on the Nutshell Deal record type — Matter_Number__c, Practice_Area__c, Billable__c, Original_Date__c, Billing_Code__c, and Duration_Minutes__c — time entry data has nowhere to land and collapses into unstructured notes. We deliver a custom-field setup plan before migration so the Deal record type is ready to accept the full matter schema.

  • Billable hours and WIP have no Nutshell accounting counterpart — financial records must be reconciled externally post-migration

    Fulcrum Snap's Ebilling Efficacy module generates LEDES 1998B-compliant invoices, tracks WIP balances, and posts directly to SAP financials. Nutshell has no invoice object, no WIP ledger, and no LEDES export capability. Every bill record migrates as a Note attached to the related Company and Deal, carrying invoice number, amount, status, and billing codes as plain text. Nutshell's own billing integration options (QuickBooks, Stripe) must be configured separately for ongoing invoicing post-migration. Firms relying on Fulcrum Snap's e-billing for client invoicing will need to establish a new billing workflow before go-live.

  • Fulcrum Snap's CSV export does not include all module data — multiple export formats must be combined for completeness

    Fulcrum Snap's Exporter tool supports CSV, XLSX, GeoJSON, PostgreSQL with PostGIS, and other formats. However, specific modules — Risk Assessment, Ebilling Efficacy, and custom SAP extension fields — may export differently or require the Downloader tool for complete record sets. We run parallel exports from both Exporter and Downloader, cross-reference record counts per module, and flag any gaps before the migration mapping is finalized. Missing records discovered after migration starts extend the timeline.

  • Fulcrum Snap user accounts map to Nutshell users by email — unmatched attorneys block record ownership assignment

    Nutshell requires a valid user account as the owner_id on any migrated record. Fulcrum Snap user records (attorneys, paralegals, billing staff) are matched to Nutshell users by email address. Any Fulcrum Snap user whose email does not correspond to a Nutshell user account is flagged pre-migration. Their records land with a fallback owner or remain unassigned pending Nutshell user creation. SAP role and permission structures (which govern matter access and billing authority in Fulcrum Snap) have no Nutshell equivalent and must be rebuilt as Nutshell roles and sharing rules after migration.

  • Conflict check results and risk assessments cannot be enforced in Nutshell — they migrate as reference notes only

    Fulcrum Snap's New Business Intake and Conflicts module produces structured conflict check results (Clear, Cleared with Notes, Conflict Found) tied to specific parties. Nutshell has no conflict-checking engine. Conflict results migrate as Notes attached to the relevant Company record, preserving the full result text and responsible party. However, Nutshell will not automatically block record creation or trigger conflict alerts. Firms that rely on Fulcrum Snap's automated conflict enforcement must establish a manual review process or a third-party conflict-checking integration before live operation in Nutshell.

Migration approach

Six steps for a successful Fulcrum Snap to Nutshell data migration

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

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

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

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

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

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

Context on both ends of the pair

Fulcrum Snap logo

Fulcrum Snap

Source

Strengths

  • SAP HANA real-time database underpins live WIP, AR, and financial dashboards across the entire firm.
  • Pre-configured legal workflows for time entry, matter management, conflicts, and e-billing ship out-of-box.
  • Supports both cloud deployment on SAP Business Technology Platform and on-premise hosting.
  • Snap Insights provides role-based analytics and intelligent alerts aligned to legal firm hierarchies.
  • Enterprise-grade security including SSO, SCIM provisioning, and audit logging on the Elite tier.

Weaknesses

  • Interface requires SAP familiarity — non-technical attorneys and staff report a significant learning curve compared to consumer-grade legal CRMs.
  • Full deployment requires SAP infrastructure licensing, making the total cost substantially higher than standalone legal platforms.
  • Customization beyond pre-configured workflows requires SAP developer resources and consultant involvement.
  • Snap Insights dashboards are configuration artifacts that cannot be directly migrated — they must be rebuilt in the destination BI layer.
  • Firms without existing SAP infrastructure face a large integration effort to connect Fulcrum Snap to their current tech stack.
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. 2 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 Fulcrum Snap and Nutshell.

  • Object compatibility

    B

    2 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

    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

    B

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

Estimator

Estimate your Fulcrum Snap 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 Fulcrum Snap to Nutshell data migrations

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

Can't find your answer?

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 consultation

Most Fulcrum Snap to Nutshell migrations complete in 48–72 hours for under 25,000 total records (clients, matters, time entries, and attachments). Larger deployments with active Ebilling Efficacy, Risk Assessment, and multiple custom SAP extension fields extend to 7–10 days. The longest planning step is mapping Fulcrum Snap's matter hierarchy to Nutshell's Deal-plus-custom-field model and enumerating every custom field that needs to be created before data lands. A 100–200 record sample migration with field-level diff typically runs within the first two days.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Fulcrum Snap.
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