CRM migration
Field-level mapping, validation, and rollback between Centerbase and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Centerbase
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Centerbase and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
Centerbase combines legal practice management with CRM, including matters, billing, time tracking, and workflow automation — built for law firms and professional services. Nutshell is a streamlined SMB CRM focused on people, companies, leads, and deal pipelines without the legal overhead. Teams moving to Nutshell typically want to shed legal-specific record types and focus purely on sales pipeline management. FlitStack AI extracts data from Centerbase via its API and file-export tools, then maps Centerbase records into Nutshell's standard objects. People and companies migrate directly. Matters (legal cases) translate into Nutshell Deals with stage and close-date mapping. Activities become Nutshell Tasks or Notes with original timestamps and owner links. Custom fields that have no direct Nutshell equivalent are preserved as custom fields on the matching object so your team can decide how to use them after migration. Workflows, automations, billing rules, and legal-specific integrations do not transfer — those must be rebuilt in Nutshell or replaced with Nutshell's email sequences and task automations. We surface a rebuild reference before the migration runs so your admin knows what was in Centerbase.
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 Centerbase 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.
Centerbase
Person
Nutshell
Person
1:1Centerbase People map directly to Nutshell People. Name, email, phone, address, and custom fields migrate 1:1. Owner resolution happens by email match against Nutshell users before records land. If duplicate emails exist, we flag them for manual review to prevent overwriting existing contacts.
Centerbase
Company
Nutshell
Company
1:1Centerbase Companies map to Nutshell Companies. Company name, domain, industry, employee count, and annual revenue fields translate directly. Multi-address companies use the primary address as the Nutshell address. Any secondary addresses are stored in a custom text field for reference.
Centerbase
Matter
Nutshell
Deal
1:1Centerbase Matters become Nutshell Deals. The Matter name maps to Deal name. Matter status (Active/Closed) maps to Nutshell's open/closed deal state. If Centerbase has multiple Matter types, each type can map to a separate Nutshell pipeline. Custom fields attached to the Matter are migrated as custom fields on the Deal.
Centerbase
Matter Stage
Nutshell
Deal Stage
1:1Each Centerbase Matter workflow stage value maps to a corresponding Nutshell pipeline stage by name or by your specified mapping table. Probabilities and forecast categories re‑apply in Nutshell after mapping. If a stage has no direct equivalent, we create a new stage in the target pipeline and flag it for your review.
Centerbase
Party / Contact Role
Nutshell
Person (secondary link)
1:1Party roles within a Matter (e.g., Plaintiff, Defendant, Client) that are not the primary Person record attach as secondary links in Nutshell. We use Person-to-Company associations and a custom role field to preserve which party role each person played in each Matter.
Centerbase
Activity (Call/Email/Task)
Nutshell
Activity / Note
1:1Centerbase activities attached to Matters — calls, emails, tasks, and notes — migrate as Nutshell Activities linked to the matching Person or Deal. Original timestamps and owner IDs are preserved. High-volume activity threads can be attached as Nutshell Notes for compact migration.
Centerbase
Document / Attachment
Nutshell
Attachment
1:1Documents attached to Matters are re‑uploaded as Nutshell Attachments linked to the matching Person or Deal. File size limits apply — files over 25MB are flagged for manual handling. We preserve the original file name and any metadata available from Centerbase.
Centerbase
Custom Item
Nutshell
Custom Field
1:1Centerbase custom items (configured in Item Manager) that have no direct Nutshell equivalent become Nutshell custom fields on the matching object. We create the custom field in Nutshell before migration and migrate all historical values. Your team decides whether to use the field going forward.
Centerbase
Billing / Time Entry
Nutshell
Note (reference only)
1:1Centerbase billing records, time entries, and trust transactions have no Nutshell equivalent — Nutshell has no native billing module. We export these as a structured CSV reference file and a Note on the associated Deal so your accounting team can access the history offline.
Centerbase
Workflow / Automation
Nutshell
Email Sequence / Task Automation
1:1Centerbase Matter-triggered workflows (stage-change triggers, document merges, email alerts) do not migrate. We export the workflow definitions as a text reference so your Nutshell admin can rebuild equivalent email sequences or task rules. Nutshell's sequence model differs fundamentally from Matter-stage triggers.
Centerbase
Report
Nutshell
Not migrated
1:1Centerbase custom reports cannot transfer — they reference Centerbase‑specific fields and formulas. We export the report definitions as a reference document. Nutshell's list and board views replace most report use cases without custom configuration, and you can build new reports in Nutshell using its built‑in reporting tools.
Centerbase
User / Owner
Nutshell
User
1:1Centerbase users are matched to Nutshell users by email address. Unmatched owners are flagged before migration so your team can either create the Nutshell user or reassign the records to an existing owner. No record lands without a valid owner reference.
| Centerbase | Nutshell | Compatibility | |
|---|---|---|---|
| Person | Person1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Matter Stage | Deal Stage1:1 | Fully supported | |
| Party / Contact Role | Person (secondary link)1:1 | Fully supported | |
| Activity (Call/Email/Task) | Activity / Note1:1 | Fully supported | |
| Document / Attachment | Attachment1:1 | Fully supported | |
| Custom Item | Custom Field1:1 | Fully supported | |
| Billing / Time Entry | Note (reference only)1:1 | Fully supported | |
| Workflow / Automation | Email Sequence / Task Automation1:1 | Fully supported | |
| Report | Not migrated1:1 | Fully supported | |
| User / Owner | User1: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.
Centerbase gotchas
Images do not transfer in Centerbase report and document exports
Workflow definitions require manual rebuild on non-Centerbase destinations
Billing records carry nested LEDES codes and origination data that require explicit mapping
Trust account three-way reconciliation rules do not transfer automatically
Platform update cycles can break migrated workflows at the destination
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
Extract Centerbase data via API and file export
FlitStack AI connects to Centerbase using your API credentials (read-only scope) and pulls People, Companies, Matters, Activities, and custom item records in paginated batches. We also use Centerbase's built-in export tools for report-style data that is easier to extract via file than via API. All records are downloaded with their original created_date, modified_date, and owner_id fields intact before any transformation begins.
Map Centerbase schema to Nutshell objects and create missing custom fields
We compare the extracted Centerbase field list against Nutshell's standard object schema. Fields with direct equivalents map automatically. Fields with no Nutshell equivalent are proposed as custom fields — we create them in your Nutshell instance (Settings > Custom Fields) before the migration loads data. We deliver a field-mapping plan showing every decision so your admin can approve or adjust before the run.
Resolve owners and validate relationship integrity
Centerbase owner IDs and attorney assignments are resolved against Nutshell users by email address. Any Centerbase user without a matching Nutshell account is flagged with the record ID and current owner name. Your team either creates the Nutshell user first or reassigns those records to a designated fallback owner. Matter-to-Person relationships (Party roles) are validated to ensure the Person record exists in Nutshell before the Matter maps to a Deal.
Run a sample migration with field-level diff
A representative slice — typically 100–500 records spanning people, companies, deals, and activities — migrates first. We generate a field-level diff that compares each Centerbase source value with its corresponding Nutshell destination value, highlighting owner resolution, stage mapping, custom field population, and relationship integrity. You can review the diff report, request adjustments to the mapping, and approve the sample before the full migration commits. This step ensures any schema or mapping issues are caught early, reducing risk for the final data load.
Execute full migration with delta-pickup and rollback plan
The full dataset loads into Nutshell in sequence (Companies, then People, then Deals, then Activities) to respect foreign-key dependencies. A 24–48 hour delta-pickup window captures any records modified in Centerbase during cutover. All operations are logged in an audit trail. If reconciliation finds unexpected gaps, a one-click rollback reverts the Nutshell state to pre-migration so your team can correct the mapping and re-run without data loss.
Platform deep dives
Centerbase
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 Centerbase 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
Centerbase: Not publicly documented..
Data volume sensitivity
Centerbase 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 Centerbase to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Centerbase 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 Centerbase
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.