CRM migration
Field-level mapping, validation, and rollback between FilePro and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
FilePro
Source
Nutshell
Destination
Compatibility
11 of 11
objects map 1:1 between FilePro and Nutshell.
Complexity
BStandard
Timeline
3–5 days
Overview
FilePro is a flat-file legal practice management DBMS built around client-matters, time tracking, and trust accounting — it has no native API and exports via delimited ASCII, CSV, or Word formats using filePro's EXPORT command. Nutshell is a cloud CRM with a structured object model: People, Companies, Leads, Deals, Tasks, and Notes; it supports custom fields on People, Companies, and Leads via its JSON-RPC API and CSV import. The migration requires extracting FilePro data in CSV format, reconciling its two-level hierarchy (client → matter) into Nutshell's flat object graph (People linked to Companies, with Deals representing matters), and recreating FilePro custom fields as Nutshell custom fields. FlitStack sequences the migration as: raw export from FilePro, CSV normalization, custom field provisioning in Nutshell, People/Companies load, then Deals with owner resolution by email. Trust balance and billable-hours data have no native Nutshell equivalent — these move as custom number fields. Workflows and automations do not migrate and must be rebuilt in Nutshell after cutover. A 24–48 hour delta pickup window captures any FilePro changes during the switchover.
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 FilePro 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.
FilePro
Client
Nutshell
People
1:1FilePro's client record maps 1:1 to Nutshell People. The client's name fields map to Nutshell's firstname and lastname; email and phone map directly. If FilePro stores multiple contacts per client file, each contact row becomes a separate Nutshell People record.
FilePro
Client
Nutshell
Companies
1:1When a FilePro client file includes a firm or organization name (common for commercial clients), that name maps to a Nutshell Company record. Each client can optionally link to one primary Company for address and industry data. If the client file contains multiple branch offices, each branch can be created as a separate Company record linked to the same People entry.
FilePro
Matter
Nutshell
Deals
1:1Each FilePro matter becomes a Nutshell Deal. The matter number or name becomes the Deal name; matter type (property, litigation, commercial) maps to a Nutshell custom field rather than a pipeline, since Nutshell uses a single pipeline model. This approach ensures that all matter metadata is searchable in Nutshell's filters and reports.
FilePro
User-defined field (matter-level)
Nutshell
Custom Field on Deal
1:1FilePro user-defined fields on matter records (e.g., matter_type, matter_reference, opposing_counsel) need Nutshell custom fields created per field. Nutshell supports custom fields on People, Companies, and Deals but not custom objects. During provisioning, we assign the appropriate field type (text, number, pick‑list, or date) based on the data content. If a FilePro field contains a limited set of values, we recommend a pick‑list to preserve consistency in Nutshell.
FilePro
Billable hours
Nutshell
Custom Field (Number) on Deal
1:1Billable hours total per matter has no native Nutshell equivalent. We create a custom Number field Billable_Hours__c on the Deal object and populate it from FilePro's time-tracking totals. This field can be used in Nutshell reports to show total billed time per client or matter, and it can be included in dashboards alongside other financial metrics.
FilePro
Trust balance
Nutshell
Custom Field (Number) on Deal
1:1FilePro's trust account balance per matter migrates as a custom Number field Trust_Balance__c on the Deal. Nutshell does not have accounting primitives — this field is for reference and reporting, not reconciliation. You can include Trust_Balance__c in custom reports to monitor historical trust balances, but any real‑time trust accounting must remain in a dedicated practice‑management or accounting system.
FilePro
Time entry
Nutshell
Tasks
1:1FilePro time entries linked to a matter map to Nutshell Tasks on the corresponding Deal. Each task records the date, narrative description, and duration. Billed vs. unbilled status is preserved as a custom pick-list field on the task. The task subject can be set from the time entry description, and the due date defaults to the entry date unless a different deadline is specified.
FilePro
Document / attachment
Nutshell
Notes
1:1FilePro stores documents against matter records. We extract file names and attach them as Nutshell Notes on the relevant Deal. Binary file re-hosting is not included — document URLs are preserved as text notes for manual re-upload. If you need the actual files migrated, FlitStack can coordinate with your IT team to transfer them to a cloud storage service and link the URLs within Nutshell Notes.
FilePro
Owner / billable contact
Nutshell
People (owner) assigned via Owner field
1:1FilePro's owner is identified by initials or contact reference within the matter. We resolve each owner by matching their email against Nutshell users and set the resolved user as the Deal owner. Unmatched owners are flagged before migration. If multiple contacts share the same email domain, we use additional attributes such as first name or firm name to improve matching accuracy.
FilePro
Matter status
Nutshell
Deal Stage
1:1FilePro matter status values (open, pending, closed, on-hold) map to Nutshell Deal stage values. The mapping is configured per your Nutshell pipeline stage setup before migration begins. You can adjust stage names and add custom stages in Nutshell, and FlitStack will update the mapping accordingly to ensure accurate status translation.
FilePro
Source system ID
Nutshell
Custom Field (Text) on each record
1:1FilePro's internal record ID is stored as Source_ID__c on each Nutshell record. This enables delta-run de-duplication and traceability back to the source system for reconciliation. During subsequent delta syncs, the Source_ID__c field allows FlitStack to match updated records in FilePro to their existing Nutshell counterparts without creating duplicates.
| FilePro | Nutshell | Compatibility | |
|---|---|---|---|
| Client | People1:1 | Fully supported | |
| Client | Companies1:1 | Fully supported | |
| Matter | Deals1:1 | Fully supported | |
| User-defined field (matter-level) | Custom Field on Deal1:1 | Fully supported | |
| Billable hours | Custom Field (Number) on Deal1:1 | Fully supported | |
| Trust balance | Custom Field (Number) on Deal1:1 | Fully supported | |
| Time entry | Tasks1:1 | Fully supported | |
| Document / attachment | Notes1:1 | Fully supported | |
| Owner / billable contact | People (owner) assigned via Owner field1:1 | Fully supported | |
| Matter status | Deal Stage1:1 | Fully supported | |
| Source system ID | Custom Field (Text) on each record1: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.
FilePro gotchas
No REST API — export depends on native EXPORT utility
User Defined Fields are firm-specific with no published schema
Actionstep acquisition creates migration scope ambiguity
Document paths exported as registry, not file bodies
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 FilePro data via EXPORT command
FlitStack guides your FilePro administrator through running the EXPORT command for each file (clients, matters, time entries, contacts). Data is extracted in CSV or delimited ASCII format. We review the raw output to confirm field order, delimiter configuration, and date format before proceeding to normalization. We also check for any non‑standard characters, embedded line breaks, or inconsistent quoting that could cause parsing errors. If the export includes multiple record types in a single file, we will split them into separate CSVs before mapping.
Audit source schema and provision Nutshell custom fields
We review the FilePro export to identify all user-defined fields and map each to a Nutshell custom field (on People, Companies, or Deals). You create the custom fields in Nutshell using our provisioning checklist before data load begins. We also configure pipeline stages to match FilePro matter status values. If any user‑defined field references another record (e.g., a lookup to a related client), we will convert it to a text field and note it for manual review after migration. We also verify that pick‑list values in FilePro map cleanly to Nutshell's allowed options.
Normalize CSV and run a test migration
The FilePro CSV is normalized: column headers are renamed to match Nutshell field names, date formats are converted to ISO 8601, and multi-value fields are split. A representative sample (typically 100–500 records) migrates first. We generate a field-level diff showing source vs. destination values for every mapped field so you can verify the mapping before committing to the full run.
Run full migration with owner resolution and activity load
The full migration loads People and Companies first (to establish contacts and account links), then Deals (matters) with resolved owners and custom field values, then Tasks (time entries) linked to the correct Deals. Binary documents are listed as Notes with file names and original paths for manual re-upload. During this phase we also validate that each Deal’s owner has a corresponding Nutshell user account, and we flag any contacts missing email addresses that prevent automatic assignment. All record IDs from FilePro are preserved in custom fields to support future delta syncs.
Cut over with delta pickup and post-migration reconciliation
After the full load, a delta-pickup window (24–48 hours) captures any FilePro records created or modified during cutover. We run a record-count reconciliation against the FilePro export totals and surface any gaps. One-click rollback is available if reconciliation fails. Your team then completes manual trust accounting verification in your practice management system and re-uploads documents to Nutshell. We also generate a detailed migration report that lists each record’s source ID, the target Nutshell ID, and any warnings encountered during the load. This report serves as a reference for your post‑go‑live audit.
Platform deep dives
FilePro
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 FilePro 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
FilePro: Not applicable — no REST API.
Data volume sensitivity
FilePro 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 FilePro to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your FilePro 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 FilePro
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.