CRM migration
Field-level mapping, validation, and rollback between Aderant Expert and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Aderant Expert
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between Aderant Expert and Nutshell.
Complexity
BStandard
Timeline
3–5 business days
Overview
Aderant Expert is a legal practice management and financial management suite — not a CRM — meaning every object has to be reconsidered against Nutshell's Account/Contact/Deal model. Clients become Nutshell Accounts; matters become Nutshell Deals (with a custom Matter_Number__c field); attorneys become Nutshell Contacts tagged with a role indicator. Aderant's time entries, billing rates, and billing types have no native Nutshell equivalent — FlitStack preserves them as custom fields on the Deal and Account records. The most significant structural gap is Aderant's many-to-many matter-to-attorney assignment: Nutshell Deals support a single primary owner; secondary attorneys are stored in a custom Multi_Attorney__c text field as a comma-separated reference list for admin reconstruction. Aderant runs on Microsoft SQL Server (desktop or RDP-hosted), so extraction requires a database read-only account rather than an API key — this affects scoping because the migration engineer needs SQL credentials, not just a login. We do not migrate Aderant's billing workflow logic, e-billing guidelines, or billing rules because those are destination-side configuration problems. We do preserve the billing type pick-list (hourly, fixed fee, contingency) as a custom field and the credit limit as a custom field on the Account, so the numbers are available for rebuilding in Nutshell's financial tools.
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 Aderant Expert 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.
Aderant Expert
Client (Aderant Matter table, client columns)
Nutshell
Account
1:1Aderant's Client record (firm name, address, phone) maps directly to a Nutshell Account. Client credit limits, billing terms, and client numbers stored as custom Account fields (Client_Credit_Limit__c, Billing_Terms__c, Client_Number__c) because Nutshell has no native billing fields. Primary attorney on the matter becomes the Account's primary contact.
Aderant Expert
Matter (Aderant Matter table, matter columns)
Nutshell
Deal
1:1Aderant matters map to Nutshell Deals. Matter number, description, practice area, billing type, and open date migrate as custom Deal fields (Matter_Number__c, Practice_Area__c, Billing_Type__c, Matter_Open_Date__c). Nutshell's StageName pick-list replaces Aderant's matter status; the migration engineer creates a stage mapping (e.g., Open → 'Negotiation', Closed Won → 'Won') before the run.
Aderant Expert
Attorney / Timekeeper
Nutshell
Contact + User
1:1Each Aderant attorney record becomes a Nutshell Contact (name, email, phone, title). If the attorney will log into Nutshell as a user, FlitStack resolves their email against Nutshell users to set OwnerId on their responsible deals. Attorneys without Nutshell user accounts are flagged for your admin to create accounts or assign a fallback owner before the migration run.
Aderant Expert
Matter-Attorney assignment (many-to-many join)
Nutshell
Deal Contact Role + custom field
many:1Aderant allows N attorneys per matter with individual roles and billing rates. Nutshell Deals have one owner and Contact Roles for secondary contacts. FlitStack maps the primary billing attorney to the Deal owner and the full N-attorney list to a custom text field (Multi_Attorney_Reference__c) storing 'AttorneyID|Name|Role|Rate' per attorney, comma-delimited, as a rebuild reference. Contact Roles are created for attorneys who also appear as Contact records.
Aderant Expert
Time Entry (billable hours)
Nutshell
Custom Activity field on Deal
1:1Aderant time entries (date, attorney, matter, hours, description) have no direct Nutshell equivalent. FlitStack aggregates time entry totals per matter into a custom field (Total_Billable_Hours__c) on the Deal. Individual time entries are preserved in a CSV export delivered alongside the Nutshell migration, so your team can reload the detail into a time-tracking tool of choice.
Aderant Expert
Bill / Invoice (Aderant Billing module)
Nutshell
Custom field on Account / Deal
1:1Aderant invoices and their line items (fees, expenses, LEDES codes) have no Nutshell equivalent. FlitStack preserves invoice number, total amount, outstanding balance, and last payment date as custom fields on the associated Account (Last_Invoice_Amount__c, Outstanding_Balance__c) and Deal (Invoice_Number__c). Detailed invoice line items are exported to CSV for manual reference or import into a dedicated billing tool.
Aderant Expert
Task / Deadline (Aderant docketing)
Nutshell
Task
1:1Aderant deadline and docketing tasks map to Nutshell Tasks attached to the corresponding Deal. Original due dates and task descriptions are preserved. Aderant's responsible-attorney field maps to Nutshell's Task owner (resolved by email). Tasks without a matching attorney are assigned to the Deal owner.
Aderant Expert
Document / File attachment
Nutshell
File (Nutshell attachments)
1:1Aderant document links and file attachments associated with matters are re-uploaded to Nutshell Files attached to the corresponding Deal or Account. Nutshell's file size limit (25MB per file) applies; documents exceeding this are noted in the migration report for manual handling.
Aderant Expert
Conflict Check record
Nutshell
Custom field on Account
1:1Aderant's conflict check records and their disposition (cleared, waivable, new conflict) have no Nutshell equivalent. FlitStack preserves conflict check status and date as custom fields on the Account (Conflict_Check_Status__c, Conflict_Check_Date__c). The conflict check workflow itself — the process logic — must be rebuilt manually in Nutshell or a third-party conflicts tool.
Aderant Expert
System ID and source reference
Nutshell
Custom field on all objects
1:1Aderant's internal matter IDs and client IDs are stored as custom fields (Aderant_Matter_ID__c, Aderant_Client_ID__c) on every Nutshell record they originate from. These IDs enable delta-run de-duplication, audit traceability, and cross-referencing back to the Aderant database for reconciliation after cutover. The IDs are written to every record at migration time, ensuring that subsequent delta runs can match source records to destination records without ambiguity even when record names or numbers change in the source system during the migration window.
| Aderant Expert | Nutshell | Compatibility | |
|---|---|---|---|
| Client (Aderant Matter table, client columns) | Account1:1 | Fully supported | |
| Matter (Aderant Matter table, matter columns) | Deal1:1 | Fully supported | |
| Attorney / Timekeeper | Contact + User1:1 | Fully supported | |
| Matter-Attorney assignment (many-to-many join) | Deal Contact Role + custom fieldmany:1 | Fully supported | |
| Time Entry (billable hours) | Custom Activity field on Deal1:1 | Fully supported | |
| Bill / Invoice (Aderant Billing module) | Custom field on Account / Deal1:1 | Fully supported | |
| Task / Deadline (Aderant docketing) | Task1:1 | Fully supported | |
| Document / File attachment | File (Nutshell attachments)1:1 | Fully supported | |
| Conflict Check record | Custom field on Account1:1 | Fully supported | |
| System ID and source reference | Custom field on all objects1: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.
Aderant Expert gotchas
Direct SQL Server database access required for migration
Accruing time entries require post-cutover delta pass
Trust account balances are point-in-time sensitive
Document binary migration is not supported
Custom fields vary per firm configuration
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
Establish Aderant SQL Server read access and run pre-migration data audit
FlitStack's migration engineer works with your Aderant administrator to obtain a read-only SQL Server account with access to the Aderant database. We run a schema discovery query against the database to identify all tables, custom columns, and relationships in use. This audit produces a data dictionary showing exactly which Aderant fields exist, which contain data, and which are custom additions. The audit also identifies any data quality issues (duplicate client records, orphaned matter entries, NULL-heavy columns) so your team can decide whether to clean before migration or accept the known gaps in Nutshell.
Create Nutshell custom fields for all non-standard Aderant data
Using the data audit as input, FlitStack delivers a Nutshell custom field setup plan listing every Aderant field that has no direct Nutshell equivalent — Matter_Number__c, Practice_Area__c, Billing_Type__c, Client_Credit_Limit__c, Multi_Attorney_Reference__c, Aderant_Matter_ID__c, and all other custom fields. Your Nutshell admin creates these fields in Settings before the test migration runs. Fields are created with appropriate types (text, picklist, date, currency, number) as specified in the plan. FlitStack validates the field configuration before proceeding to the test migration step.
Run a sample matter migration with field-level diff
FlitStack extracts a representative slice from Aderant — typically 100–300 matters spanning different practice areas, billing types, and matter statuses, plus all associated attorneys and clients — and loads them into Nutshell. We generate a field-level diff comparing source values against destination values for every mapped field. You review the diff to verify that practice area mapping is correct, billing type pick-list values are as expected, attorney resolution produced the correct owner assignments, and the Multi_Attorney_Reference__c field contains the expected structured data. Any mapping corrections are made before the full migration run commits.
Execute full migration with delta-pickup cutover window
FlitStack runs the full data migration against Nutshell's JSON-RPC API. A delta-pickup window opens at the time of cutover — typically 24–48 hours — during which any matters, clients, or attorney records created or modified in Aderant after the migration snapshot are captured and written to Nutshell. This window ensures that if your team continues working in Aderant during the cutover period, no net-new records are lost. All API operations are logged to an audit trail. After the delta window closes, FlitStack runs a reconciliation count comparing Aderant record totals against Nutshell record totals for each object type.
Deliver reconciliation report and rebuild reference documents
FlitStack delivers a full reconciliation report showing record counts by object type, any records that failed to migrate with error reasons, and a field-level validation summary. Time entry aggregates and invoice detail CSVs are delivered alongside the Nutshell migration. We also provide a rebuild reference document for your Nutshell admin: the complete mapping plan, the Multi_Attorney_Reference__c field contents for every deal with multiple attorneys, and the conflict check status for every account. This document is the blueprint for rebuilding multi-attorney assignments, e-billing workflows, and any automation logic that was not migratable.
Platform deep dives
Aderant Expert
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Aderant Expert and Nutshell.
Object compatibility
1 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
Aderant Expert: Not applicable — no public API.
Data volume sensitivity
Aderant Expert 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 Aderant Expert to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Aderant Expert 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 Aderant Expert
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.