CRM migration

Migrate from Centerbase to Nutshell

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

Centerbase logo

Centerbase

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Centerbase and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

Centerbase logo

Centerbase

What's pushing teams away

  • Platform updates occasionally break existing workflows and functionality, requiring support intervention to restore — a pattern confirmed across multiple G2 reviews citing frustration with update-related regressions.
  • Reporting is difficult to navigate and often fails to produce the exact output firms need, with specific firm requirements frequently unmet by the built-in report writer.
  • Inconsistent customer support response times and quality create friction when issues arise, particularly during or after the implementation phase.
  • The interface is described as overwhelming by new users with a steep learning curve that requires significant training investment before staff can operate efficiently.

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

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

maps to

Nutshell

Person

1:1
Fully supported

Centerbase 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

maps to

Nutshell

Company

1:1
Fully supported

Centerbase 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

maps to

Nutshell

Deal

1:1
Fully supported

Centerbase 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

maps to

Nutshell

Deal Stage

1:1
Fully supported

Each 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

maps to

Nutshell

Person (secondary link)

1:1
Fully supported

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

maps to

Nutshell

Activity / Note

1:1
Fully supported

Centerbase 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

maps to

Nutshell

Attachment

1:1
Fully supported

Documents 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

maps to

Nutshell

Custom Field

1:1
Fully supported

Centerbase 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

maps to

Nutshell

Note (reference only)

1:1
Fully supported

Centerbase 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

maps to

Nutshell

Email Sequence / Task Automation

1:1
Fully supported

Centerbase 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

maps to

Nutshell

Not migrated

1:1
Fully supported

Centerbase 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

maps to

Nutshell

User

1:1
Fully supported

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

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.

Centerbase logo

Centerbase gotchas

High

Images do not transfer in Centerbase report and document exports

Medium

Workflow definitions require manual rebuild on non-Centerbase destinations

Medium

Billing records carry nested LEDES codes and origination data that require explicit mapping

Medium

Trust account three-way reconciliation rules do not transfer automatically

Low

Platform update cycles can break migrated workflows at the destination

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

  • Matter-type to pipeline mapping requires pre-migration schema decisions

    Centerbase supports multiple Matter types (e.g., Litigation, Corporate, Family Law) each with their own workflow stages. Nutshell pipelines isolate stage values per pipeline. If your Centerbase setup uses more than one Matter type, you must decide how to map each to a Nutshell pipeline before migration. We cannot resolve this automatically because the mapping changes which stages appear on each deal. We deliver a Matter-type-to-pipeline mapping plan before data moves so your Nutshell admin can pre-create the pipelines and stages.

  • Billing and time-entry data has no Nutshell destination — preserved as reference only

    Centerbase's integrated legal billing module stores time entries, trust transactions, LEDES invoice data, and billing codes. Nutshell has no billing or accounting module at all — this is a design gap, not a missing feature. We export all billing-related records as a structured CSV file and attach it as a Note on the migrated Deal so your accounting team can access the history offline. Any financial reporting on billing data must be rebuilt in a separate accounting tool after migration.

  • Workflow automations cannot migrate — legal triggers have no Nutshell equivalent

    Centerbase workflows trigger on Matter stage changes, document generation, and billing events. Nutshell's automation model is limited to email sequences triggered by lead entry or stage changes plus task-creation rules. There is no equivalent to Matter-stage-triggered document merges or legal-specific workflow sequences. We export your workflow definitions as a text reference document so your Nutshell admin can rebuild equivalent sequences or determine which automations to drop. This is disclosed upfront in the migration plan, not discovered after the run.

  • Custom items become custom fields — field type differences require review

    Centerbase custom items configured in Item Manager can have complex field types including lookup relationships, grouped records, and multi-select pick-lists. Nutshell custom fields support text, number, date, pick-list, and boolean types but do not support lookup relationships between custom items. Complex custom item structures may need to be flattened into a custom field or split across multiple custom fields on the Person or Deal. We document each custom item's structure and propose a flattening strategy before migration.

  • API rate limits on Centerbase can extend extraction timelines

    Centerbase's public API (documented via Notion) imposes per‑token rate limits that can throttle bulk extraction during the migration window. FlitStack AI implements retry logic with exponential backoff and paginates all list endpoints to stay within the allowed request quota. For large data sets exceeding 50,000 records, we schedule extraction during off‑peak hours to avoid hitting throttling thresholds that could extend the timeline. If the API continues to be constrained, we can supplement with Centerbase's file‑export tools to pull report‑style data, ensuring the migration stays on schedule without compromising data integrity.

Migration approach

Six steps for a successful Centerbase to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

Centerbase logo

Centerbase

Source

Strengths

  • All-in-one cloud platform consolidates practice management, billing, and accounting without requiring external accounting software.
  • Deep customization of fields, workflows, and matter structures accommodates firm-specific processes at scale.
  • Legal-specific features including IOLTA trust accounting, LEDES export, and origination fee tracking meet bar compliance requirements.
  • Certified partner onboarding with structured implementation phases reduces risk on migration from legacy systems like Time Matters.
  • Custom report writer with cross-database export and import enables firms to move reporting templates between environments.

Weaknesses

  • Steep learning curve and overwhelming interface require significant training investment before staff productivity is achieved.
  • Platform updates occasionally break existing functionality, requiring support intervention to restore normal operations.
  • Inconsistent customer support response times create friction during issue resolution, particularly post-implementation.
  • Reporting is difficult to navigate and frequently fails to deliver the exact output firms need without custom report work.
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 Centerbase 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

    Centerbase: Not publicly documented..

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Centerbase-to-Nutshell migrations complete in 48–72 hours for under 25,000 total records. Larger setups with multiple Matter types, heavy custom item usage, or more than 100,000 records extend to 5–10 days. The longest planning step is typically the Matter-type-to-pipeline mapping decision — your Nutshell admin needs to pre-create pipelines and stages before data lands. We handle extraction, mapping, and loading; your admin handles the Nutshell-side schema setup in parallel.

Adjacent paths

Related migrations to explore

Ready when you are

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