CRM migration

Migrate from Bilr to Nutshell

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

Bilr logo

Bilr

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Bilr and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Bilr is a legal-practice CRM built around client and matter management with integrated billing and time-tracking features. Nutshell is a general SMB CRM organized around People, Companies, Leads, and Deals with visual pipeline management. The migration challenge is translating Bilr's matter-centric model into Nutshell's sales-deal model while preserving the legal context that lives in Bilr's custom fields, practice-area tags, and attorney assignments. We map Bilr clients to Nutshell People, Bilr matters to Nutshell Deals with a custom Matter_Number__c field, Bilr practice-area tags to Nutshell pipeline stages, and Bilr attorney assignments to a custom Attorney__c field on each deal record. Activities (notes, tasks, emails) migrate as Nutshell Activities linked to the corresponding People or Deal record with original timestamps and owners preserved. Nutshell's custom field system accommodates Bilr's legal-specific properties that have no direct Nutshell equivalent — for example, original matter numbers or billing arrangements. Workflows, billing rules, time-tracking setups, and trust accounting logic do not migrate. These must be rebuilt in Nutshell or retained in Bilr for ongoing billing needs. Nutshell's Import2 tool supports CSV imports, but large or complex Bilr exports benefit from our API-to-API migration engine, which handles field-level validation and delta-pickup during cutover.

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

Bilr logo

Bilr

What's pushing teams away

  • No trust accounting capability means firms subject to IOLTA requirements must run a separate system or leave the platform entirely
  • Limited customization options for templates and workflows frustrate firms with non-standard billing arrangements or practice-area-specific needs
  • Mid-tier and Advanced pricing at $45–55 per user per month scales cost-prohibitively for larger firms evaluating against all-in-one legal practice management suites
  • Smaller ecosystem and fewer integrations compared to dominant legal platforms creates friction for firms needing calendar, document, or accounting sync

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

Each row shows how a Bilr 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.

Bilr

Client

maps to

Nutshell

Person

1:1
Fully supported

Bilr's client record maps directly to Nutshell Person. Client name splits into firstName and lastName where present; single-name clients preserve the full name in firstName. Primary contact email, phone, and address fields map directly. Multi-contact clients require additional Person records linked to the same company.

Bilr

Client Company

maps to

Nutshell

Company

1:1
Fully supported

Bilr's client organization (law firm or corporate legal department) maps to Nutshell Company. Company name, website, industry, and address fields migrate directly. Parent-subsidiary relationships in Bilr map to Nutshell's parent company field. Multi-office clients collapse to one primary Company record in Nutshell.

Bilr

Matter

maps to

Nutshell

Deal

1:1
Fully supported

Bilr matters are the primary unit of work in the source platform. Each matter maps to a Nutshell Deal with a custom Matter_Number__c field holding the original Bilr matter identifier. Matter status (open, closed, pending) maps to Nutshell Deal stage. Matter description migrates as the Deal description field. Billing arrangement and retainer status migrate as custom fields on the deal.

Bilr

Practice Area

maps to

Nutshell

Pipeline / Stage

1:1
Fully supported

Bilr practice areas (e.g., Litigation, Corporate, Real Estate) map to Nutshell pipeline stages. If Bilr uses multiple practice-area tags per matter, the migration creates one Deal per matter and tags the dominant practice area as the stage; additional practice areas preserve as a custom multi-select field on the Deal.

Bilr

Attorney / Responsible Attorney

maps to

Nutshell

Custom field on Deal (Attorney__c) + Nutshell Owner resolution

1:1
Fully supported

Bilr's attorney assignment maps to a custom Attorney__c text field on the Nutshell Deal for reference. Owner resolution attempts to match the attorney's email to a Nutshell user; matched users become the Deal owner. Unmatched attorneys are flagged so your team can assign them to Nutshell users before the full migration runs.

Bilr

Staff Assignment

maps to

Nutshell

Custom field on Deal (Paralegal__c / Staff__c)

1:1
Fully supported

Bilr's non-attorney staff assignments on matters map to custom text fields on the Nutshell Deal. Nutshell does not have a native staff-assignment model on Deals, so these are preserved as reference fields. Multiple staff members are comma-separated in the custom field value.

Bilr

Activity / Note

maps to

Nutshell

Task

1:1
Fully supported

Bilr notes, communications log entries, and meeting records map to Nutshell Tasks. Subject line maps to Task name, body maps to Task description, and created date maps to the original timestamp. Each Task is linked to the corresponding Person and Deal record by reference ID. Activity type (call, email, meeting) maps to Task category or a custom activity-type field.

Bilr

Document / File Attachment

maps to

Nutshell

File / Attachment

1:1
Fully supported

Bilr documents attached to matters are downloaded and re-uploaded to the corresponding Nutshell Deal record. File size limits follow Nutshell's attachment constraints. Documents that exceed size limits are flagged for manual handling. Inline images in notes are extracted and rehosted as separate file attachments.

Bilr

Billing Rate / Fee Arrangement

maps to

Nutshell

Custom field on Deal (Fee_Arrangement__c)

1:1
Fully supported

Bilr billing rates and fee arrangements (hourly, flat, contingency) have no Nutshell equivalent. These migrate as a custom text or pick-list field (Fee_Arrangement__c) on the Deal. Actual invoice history and trust ledger records do not migrate — those stay in Bilr for billing continuity.

Bilr

Trust Balance / Retainer

maps to

Nutshell

Custom field on Deal (Trust_Balance__c)

1:1
Fully supported

Bilr trust accounting balances and retainer amounts have no Nutshell equivalent — Nutshell does not include trust accounting. We migrate the most recent trust balance as a custom currency field (Trust_Balance__c) on the Deal for reference, but your firm should maintain trust accounting in Bilr or a dedicated legal billing 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.

Bilr logo

Bilr gotchas

High

No trust accounting support is a hard blocker for IOLTA firms

Medium

Limited workflow and template customization

Medium

Per-seat pricing model is migration-cost-sensitive

Low

Export scope discovery is required 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

  • Trust accounting and retainer balances have no Nutshell equivalent

    Bilr's trust accounting module — tracking retainer balances, LEDES billing codes, and client trust funds — has no counterpart in Nutshell's data model. Nutshell does not include any billing or financial-tracking capability. We migrate the most recent trust balance as a custom currency field on the Bilr Matter → Nutshell Deal mapping, but the ongoing trust ledger, client statements, and billing history must remain in Bilr or a dedicated legal billing system. Firms that rely on trust accounting should plan to maintain Bilr access for billing purposes even after the CRM migration is complete.

  • Bilr workflows and matter automations do not transfer to Nutshell

    Bilr's workflow automation for matter lifecycle, conflict checks, and email sequences has no direct Nutshell equivalent. Nutshell's automation on Pro and above covers sales email sequences and lead routing, but Bilr-specific matter-opening workflows, conflict-check triggers, and time-tracking automations must be rebuilt. We export Bilr workflow definitions as a structured reference document for your team to use when rebuilding automations in Nutshell. The migration scope is strictly data — activities, contacts, matters, and documents — not workflow logic.

  • Nutshell does not support custom fields on Deals directly

    Bilr custom fields on matters — practice area, billing arrangement, trust balance, responsible attorney — require Nutshell custom fields for storage. However, Nutshell's custom field model applies only to Companies, People, and Leads, not to Deals. Custom metadata for Deals in Nutshell requires either a custom Nutshell integration or storing the data on the associated Person or Company record as a reference. We surface this in the migration plan and propose the cleanest storage approach for each Bilr matter field before the migration runs.

  • Owner resolution on matters requires pre-mapping attorney emails

    Bilr matters are tied to attorneys and staff members by name and internal ID. Nutshell Deals have a single owner field tied to a Nutshell user account. Before the migration runs, your team must ensure that every Bilr attorney and staff member has a corresponding Nutshell user account with a matching email address. We perform email-based owner resolution as part of the migration; any Bilr attorney without a Nutshell account is flagged before the migration commits, and their matters can be assigned to a fallback Nutshell user or held pending account creation.

  • Billing rates and invoice history do not migrate

    Bilr's billing rates (hourly rates by attorney, flat fees, contingency arrangements) and full invoice history are legal-billing-specific data that has no Nutshell equivalent. Nutshell does not include invoicing, time tracking, or billing. We migrate the billing arrangement descriptor (e.g., 'Hourly $350/hr') as a custom text field on the Deal for reference, but actual rate schedules, time entries, and invoices must remain in Bilr or be migrated separately to a dedicated billing system. Firms planning to stop using Bilr entirely should budget for a parallel billing-system migration.

Migration approach

Six steps for a successful Bilr to Nutshell data migration

  1. Audit Bilr schema and create Nutshell custom fields

    We extract a full field inventory from your Bilr account — all client fields, matter fields, custom fields, and activity types. We then create the corresponding Nutshell custom fields: Matter_Number__c, Attorney__c, Staff__c, Fee_Arrangement__c, Trust_Balance__c, Pipeline__c, and any other Bilr-specific fields that need a home in Nutshell. This step includes setting up the Nutshell pipeline and stage structure to reflect Bilr's practice-area taxonomy. The schema plan is delivered for your review before any data moves.

  2. Resolve attorney and staff owners by email

    We pull the list of Bilr attorneys and staff members assigned to matters. Each person's email address is matched against Nutshell user accounts. Matched users become the Nutshell Deal owner. Unmatched attorneys are flagged in a pre-migration report with instructions: either create a Nutshell account for that person or designate a fallback owner before the migration run. No Deal lands in Nutshell without a resolved owner.

  3. Run sample migration with field-level diff

    A representative slice of Bilr data — typically 100–500 records spanning clients, companies, matters, and activities — migrates to Nutshell in a test run. We generate a field-level diff report showing exactly what mapped, what transformed, and what required a custom field. You verify matter-number continuity, attorney assignment mapping, activity linking, and custom field population before the full run commits. Any mapping adjustments are made before the production migration begins.

  4. Execute full migration with delta-pickup window

    The full Bilr dataset migrates: Clients → People, Companies → Companies, Matters → Deals with custom fields, and Activities → Tasks with original timestamps and owner links. During the cutover window, FlitStack AI maintains scoped read access to Bilr. A delta-pickup run captures any new clients, matters, or activities created or modified after the initial export timestamp. Audit log records every operation, and a reconciliation count is generated against Bilr's record totals before go-live is confirmed.

  5. Reconcile, validate, and hand off rebuild reference

    Post-migration, we deliver a full reconciliation report comparing Bilr record counts against Nutshell record counts by object type. You verify that key matters are present with the correct custom field values, attorney assignments, and activity histories. We also deliver the Bilr workflow definitions as a structured export so your Nutshell admin has a rebuild reference for email sequences, matter-opening automations, and conflict-check workflows that did not migrate.

Platform deep dives

Context on both ends of the pair

Bilr logo

Bilr

Source

Strengths

  • Purpose-built for legal billing workflows with time entry, expense tracking, and invoice generation within a single platform
  • Per-user pricing from $33.99/month provides a low barrier to entry for solo practitioners and small law firms
  • Three tiers (Basic, Pro, Advanced) offer a clear upgrade path as firm size and billing complexity grow
  • 24/5 support and on-demand training included across all tiers, differentiating from platforms that charge extra for support
  • Mobile apps on iOS and Android allow attorneys to log time and review bills from outside the office

Weaknesses

  • No trust accounting or IOLTA-compliant ledger means firms with client fund requirements cannot use Bilr as their sole financial system
  • Limited workflow customization and template flexibility frustrate firms with non-standard billing arrangements or practice-area-specific needs
  • Smaller third-party integration ecosystem compared to dominant legal practice management platforms creates friction for calendar, document, and accounting sync
  • Per-seat pricing scales cost linearly, which may become expensive for larger firms with many non-billing staff who need access
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 Bilr 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

    Bilr: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your Bilr to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Small Bilr-to-Nutshell migrations — typically under 10,000 clients and matters — complete in 48–72 hours of processing time. Mid-sized setups with 10,000–50,000 records and a moderate number of custom fields generally require 3–5 days including schema setup, owner resolution, and testing. Large migrations with over 100,000 records or complex matter-to-deal custom field structures extend to 5–7 days. Nutshell's own import support via Import2 can add 24–48 business hours on top of the data movement.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Bilr.
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