CRM migration
Field-level mapping, validation, and rollback between Bilr and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Bilr
Source
Nutshell
Destination
Compatibility
10 of 10
objects map 1:1 between Bilr and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Bilr'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
Nutshell
Company
1:1Bilr'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
Nutshell
Deal
1:1Bilr 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
Nutshell
Pipeline / Stage
1:1Bilr 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
Nutshell
Custom field on Deal (Attorney__c) + Nutshell Owner resolution
1:1Bilr'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
Nutshell
Custom field on Deal (Paralegal__c / Staff__c)
1:1Bilr'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
Nutshell
Task
1:1Bilr 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
Nutshell
File / Attachment
1:1Bilr 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
Nutshell
Custom field on Deal (Fee_Arrangement__c)
1:1Bilr 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
Nutshell
Custom field on Deal (Trust_Balance__c)
1:1Bilr 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.
| Bilr | Nutshell | Compatibility | |
|---|---|---|---|
| Client | Person1:1 | Fully supported | |
| Client Company | Company1:1 | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Practice Area | Pipeline / Stage1:1 | Fully supported | |
| Attorney / Responsible Attorney | Custom field on Deal (Attorney__c) + Nutshell Owner resolution1:1 | Fully supported | |
| Staff Assignment | Custom field on Deal (Paralegal__c / Staff__c)1:1 | Fully supported | |
| Activity / Note | Task1:1 | Fully supported | |
| Document / File Attachment | File / Attachment1:1 | Fully supported | |
| Billing Rate / Fee Arrangement | Custom field on Deal (Fee_Arrangement__c)1:1 | Fully supported | |
| Trust Balance / Retainer | Custom field on Deal (Trust_Balance__c)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.
Bilr gotchas
No trust accounting support is a hard blocker for IOLTA firms
Limited workflow and template customization
Per-seat pricing model is migration-cost-sensitive
Export scope discovery is required 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
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.
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.
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.
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.
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
Bilr
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 Bilr 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
Bilr: Not publicly documented — typical SaaS limits assumed and confirmed during scoping.
Data volume sensitivity
Bilr 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 Bilr to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Bilr 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 Bilr
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.