CRM migration

Migrate from FilePro to Nutshell

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

FilePro logo

FilePro

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

11 of 11

objects map 1:1 between FilePro and Nutshell.

Complexity

BStandard

Timeline

3–5 days

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

FilePro logo

FilePro

What's pushing teams away

  • Very limited review volume and social proof — only 1 verified G2 review and 10 Capterra reviews make it hard to assess long-term satisfaction and support track record.
  • Competitive pressure from cloud-native legal CRMs like Clio, LawVu, and PracticePanther that offer modern UX, API-first architecture, and larger user communities.
  • Acquisition by Actionstep creates uncertainty about future product direction, roadmap continuity, and whether current FilePro customers remain a priority.

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

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

maps to

Nutshell

People

1:1
Fully supported

FilePro'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

maps to

Nutshell

Companies

1:1
Fully supported

When 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

maps to

Nutshell

Deals

1:1
Fully supported

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

maps to

Nutshell

Custom Field on Deal

1:1
Fully supported

FilePro 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

maps to

Nutshell

Custom Field (Number) on Deal

1:1
Fully supported

Billable 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

maps to

Nutshell

Custom Field (Number) on Deal

1:1
Fully supported

FilePro'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

maps to

Nutshell

Tasks

1:1
Fully supported

FilePro 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

maps to

Nutshell

Notes

1:1
Fully supported

FilePro 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

maps to

Nutshell

People (owner) assigned via Owner field

1:1
Fully supported

FilePro'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

maps to

Nutshell

Deal Stage

1:1
Fully supported

FilePro 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

maps to

Nutshell

Custom Field (Text) on each record

1:1
Fully supported

FilePro'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.

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.

FilePro logo

FilePro gotchas

High

No REST API — export depends on native EXPORT utility

Medium

User Defined Fields are firm-specific with no published schema

Medium

Actionstep acquisition creates migration scope ambiguity

Low

Document paths exported as registry, not file bodies

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

  • Flat-file export requires schema discovery before mapping

    FilePro has no API — data comes out via the EXPORT command in delimited ASCII or CSV format. The delimiter character, field order, and header row presence vary by FilePro configuration. Before any field mapping begins, FlitStack reviews a sample export to identify the exact column layout, date formats (DD/MM/YYYY vs. MM/DD/YYYY), and whether multi-value fields are serialized within a single column. Firms that have added user-defined fields over years may have inconsistent export schemas. We surface these findings in the pre-migration audit before any data moves.

  • Custom fields on matters require pre-provisioning in Nutshell

    Nutshell supports custom fields on People, Companies, and Deals but does not have a custom objects model. Every FilePro user-defined field on a matter record needs a corresponding Nutshell custom field created before migration. Fields that reference lookups (e.g., a FilePro field that points to another FilePro file) cannot map to Nutshell lookups — they become text fields and your Nutshell admin decides whether to populate them manually post-migration. FlitStack delivers a custom field provisioning checklist as part of the pre-migration plan so your Nutshell instance is schema-ready before the load begins.

  • Trust account balance and billable-hours totals are reference-only in Nutshell

    FilePro's trust accounting model (client trust ledgers, disbursement tracking, and billable-hours totals) has no native equivalent in Nutshell. Migrating these as custom number fields preserves the data for reporting, but Nutshell will not maintain running trust balances or flag insufficient trust funds — those are accounting responsibilities that need to remain in a dedicated practice management or accounting system. We flag this clearly in the migration plan and recommend documenting your trust reconciliation process before cutover.

  • Matter-to-Deal 1:N collapse when one client has multiple matters

    FilePro allows a single client file to hold multiple matters. In Nutshell's model, each matter becomes a separate Deal linked to the same People record. The Matter_Number__c and Matter_Type__c custom fields on each Deal preserve which matter each record represents. If FilePro stores matter-specific notes and documents, those need to be associated to the correct Deal — we map them by matter number during the activity migration step. Careful mapping of the matter identifier ensures that reports and dashboards in Nutshell reflect the correct caseload per client. Without this mapping, a single client’s matters could appear as unrelated Deals, complicating workload analysis.

  • Owner resolution by email match is approximate

    FilePro identifies billable contacts by name or initials, not email. FlitStack resolves owners by matching the contact's email address against Nutshell user accounts. Contacts that have no email in FilePro, or whose email does not match a Nutshell user, are flagged for manual owner assignment. The FilePro owner name is preserved as a custom field on the Deal so no attribution is lost even if automatic resolution fails. If multiple contacts share the same name, the system will also consider the associated firm name to improve matching accuracy.

Migration approach

Six steps for a successful FilePro to Nutshell data migration

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

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

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

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

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

Context on both ends of the pair

FilePro logo

FilePro

Source

Strengths

  • Monthly subscription model with no minimum contract terms — flexible for firms with fluctuating headcount.
  • Integrated legal practice management covering matter tracking, time capture, client accounting, and document links in one system.
  • Australian vendor with local support teams and demonstrated long-term client retention over 20-plus years.
  • Supports User Defined Fields so firms can capture firm-specific data without code changes.
  • On-premises and cloud deployment options — addresses firms with data-residency or cloud-aversion concerns.

Weaknesses

  • No conventional REST API — data extraction relies on the native EXPORT utility outputting delimited ASCII, which requires custom parsing for complex schemas.
  • Proprietary flat-file DBMS underlying FilePro means custom data structures are harder to reverse-engineer without firm-specific documentation.
  • Acquisition by Actionstep introduces roadmap uncertainty for existing FilePro customers.
  • Small review and community footprint limits peer validation and third-party plugin ecosystem.
  • Limited automation and workflow engine compared to modern cloud-native legal CRMs.
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. 1 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 FilePro and Nutshell.

  • Object compatibility

    B

    1 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

    FilePro: Not applicable — no REST API.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

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

Book a free 30 minute consultation

Small FilePro setups with clean CSV exports and fewer than 5,000 records typically complete in 3–5 days. Firms with large matter volumes, 50+ user-defined fields, or complex trust-account data extend to 10–14 days. The longest single step is usually custom-field provisioning in Nutshell and the pre-migration schema audit of the FilePro export format. Timeline also depends on the availability of a clean export from FilePro and on how quickly your team can approve the custom field provisioning checklist. Post‑migration verification of record counts and trust balances may add a few hours.

Adjacent paths

Related migrations to explore

Ready when you are

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