CRM migration

Migrate from Time Matters(r) to Nutshell

Field-level mapping, validation, and rollback between Time Matters(r) and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Time Matters(r) logo

Time Matters(r)

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

12 of 12

objects map 1:1 between Time Matters(r) and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Time Matters uses a field-based architecture on Microsoft SQL Server where nearly every visible element can be a custom field, creating dense custom schemas that vary firm-by-firm. Nutshell operates as a cloud CRM with People, Companies, Leads, and Deals as standard objects and custom fields for extensibility. Migrating Time Matters to Nutshell requires extracting from the SQL backend (or via custom export templates), resolving the field inventory against Nutshell's standard and custom field model, mapping matter-type relationships to Deals, and converting time and expense entries into Nutshell activities. FlitStack AI reads directly from Time Matters' SQL database or export files, builds a field inventory, creates the necessary Nutshell custom fields, and loads contacts, companies, deals, and historical activities via Nutshell's JSON-RPC API. Workflows, document templates, and automated rules do not migrate — those must be rebuilt in Nutshell after go-live. A delta-pickup window captures any records modified during the cutover, and one-click rollback is available if reconciliation identifies issues.

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

Time Matters(r) logo

Time Matters(r)

What's pushing teams away

  • The UI and feature set feel dated compared to cloud-first competitors like Clio, MyCase, and Smokeball that offer native mobile apps and modern automation.
  • Billing and accounting modules are widely reported as cumbersome and unintuitive, driving firms to platforms that handle legal billing natively and better.
  • Customer service scores (2.9 on Capterra) reflect frustrations with slow or unresponsive support, especially for firms on older versions.
  • The lack of a public API means no integrations, no automation hooks, and no programmatic way to extract data — forcing firms into manual CSV exports for any migration.
  • Modern competitors offer easier workflow automation; a Reddit thread comparing TimeMatters to MyCase noted that literally everything was easier in the alternative platform.

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 Time Matters(r) objects map to Nutshell

Each row shows how a Time Matters(r) 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.

Time Matters(r)

Contact

maps to

Nutshell

Person

1:1
Fully supported

Time Matters Contacts map directly to Nutshell People. The primary company link is preserved as the primary Company assignment in Nutshell. Time Matters allows N:N contact-to-company relationships — the primary company is set as the Nutshell Company link; additional relationships are noted in a custom field for reference.

Time Matters(r)

Matter

maps to

Nutshell

Deal

1:1
Fully supported

Time Matters Matters map to Nutshell Deals. Matter number, practice area, responsible attorney, and status are preserved as Nutshell custom fields on the Deal record. Matter-type (e.g., litigation, transactional, advisory) maps to a Nutshell custom field since Deals do not have a native type attribute beyond name and stage.

Time Matters(r)

Company

maps to

Nutshell

Company

1:1
Fully supported

Time Matters Companies map to Nutshell Companies using domain-based matching to detect duplicates, with each firm's parent-company hierarchy preserved via Nutshell's native parent-company field where available. When a parent-company relationship cannot be represented natively, the hierarchy is captured in a custom text field (Parent_Company__c) as a dot‑separated path, enabling manual consolidation or structure recreation after the migration.

Time Matters(r)

Event / Calendar Entry

maps to

Nutshell

Activity

1:1
Fully supported

Calendar Events in Time Matters—including appointments, hearings, and deadlines—migrate as Nutshell Activities, preserving the original start datetime, end datetime, duration, and the linked Person, Company, or Deal record. Nutshell's unified activity model treats both meetings and tasks as Activities, so each event retains its type indicator (meeting, call, task) in a custom field where needed to maintain the original classification after migration.

Time Matters(r)

ToDo / Task

maps to

Nutshell

Task

1:1
Fully supported

Time Matters ToDo items are imported as Nutshell Tasks, keeping the original due date, priority level, and completion status. The assignee is resolved by matching the Time Matters user email to a Nutshell user account; if no match exists the task is flagged for manual owner assignment. Completed tasks retain their completion timestamp, and any notes or descriptions attached to the ToDo are preserved in the Task description field.

Time Matters(r)

Note

maps to

Nutshell

Note

1:1
Fully supported

Time Matters Notes migrate to Nutshell Notes attached to the corresponding Person, Company, or Deal record. The note body text, create date, and last-modified date are preserved. Notes linked to multiple records in Time Matters are attached to the primary record and referenced in a custom field for the related records.

Time Matters(r)

Time Entry

maps to

Nutshell

Task

1:1
Fully supported

Time Matters time entries (billable hours with date, duration, and description) migrate as Nutshell Tasks of type 'Time Entry'. The original hours, date, and matter association are stored as custom fields on the Task record. Note that Nutshell does not have native billing; billable time is preserved as a reference record only.

Time Matters(r)

Expense Entry

maps to

Nutshell

Task

1:1
Fully supported

Time Matters expense entries migrate as Nutshell Tasks with a custom field capturing the expense amount, category, and matter link. Original expense date and description are preserved. Trust balance and outstanding balance snapshots at migration time are recorded as one-time values in a custom field on the associated Matter/Deal.

Time Matters(r)

Email Communication

maps to

Nutshell

Activity / Note

1:1
Fully supported

Time Matters email communications (stored as to/from/subject/body without the original email) migrate as Nutshell Notes with an activity link. The email metadata (sender, recipient, timestamp, subject) is preserved as structured fields; the message body migrates as note content. Original MIME emails require a different preservation method and are noted separately.

Time Matters(r)

Phone Communication / Call Log

maps to

Nutshell

Call

1:1
Fully supported

Phone call logs from Time Matters migrate as Nutshell Calls, preserving caller/recipient name, call date, duration, and notes. Call outcome values (answered, voicemail, missed) are stored in a custom pick-list field (Call_Outcome__c) when present in the source record. The primary contact is linked as the Call owner, and additional participants are noted in a secondary custom field for reference.

Time Matters(r)

Document / Attachment

maps to

Nutshell

File

1:1
Fully supported

Time Matters file attachments migrate as Nutshell Files. Documents are downloaded from the file server, decrypted if encrypted, and re-uploaded to Nutshell's cloud storage linked to the corresponding Person, Company, or Deal record. File name, create date, and file size are preserved. Encrypted attachments require the Time Matters admin to provide decryption access before migration.

Time Matters(r)

Custom Fields (active)

maps to

Nutshell

Custom Field

1:1
Fully supported

Each active Time Matters custom field that does not map to a standard Nutshell field is created as a Nutshell custom field on the appropriate entity (Person, Company, or Lead). Firms are encouraged to prune unused custom fields before migration to reduce Nutshell schema clutter. Fields are created as Text, Number, Date, or Picklist based on the source data type.

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.

Time Matters(r) logo

Time Matters(r) gotchas

High

No API forces file-only migration with manual export wizard steps

Medium

Archived records excluded by default — explicit 'Both' selection required

Medium

Include field names checkbox is easy to miss, leaving CSVs headerless

High

Binary documents and attachments not included in any standard export

Low

Merge template library requires separate file-share export, not in export wizard

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

  • Encrypted attachments require decryption before transfer

    Time Matters can store documents and attachments in an encrypted format that cannot be read directly from the file server. If your Time Matters database uses encrypted attachments, the migration specialist requires administrator credentials to the Time Matters file server and the decryption key or access to decrypt files before they can be re-uploaded to Nutshell's cloud storage. Encrypted attachments that cannot be decrypted are logged and excluded from the migration with a summary of the file names and sizes that were skipped, allowing your team to manually handle those records after migration.

  • Excessive custom field density requires schema pruning

    Time Matters is a field-based application where nearly every visible element can be a custom field, and firms routinely accumulate 50–200+ active custom fields across record types. Many of these fields are no longer in use but still contain data or field definitions. Nutshell supports custom fields for People, Companies, and Leads, but excessive custom field counts increase migration planning time and create schema clutter in Nutshell. We inventory every Time Matters custom field, flag fields with no data or no active use, and present a pruning recommendation before creating Nutshell custom fields. Firms that skip pruning end up with dozens of single-value or empty custom fields in Nutshell that create noise in reporting.

  • N:N contact-to-company relationships collapse to primary company

    Time Matters supports many-to-many relationships between Contacts and Companies, where a single contact can be associated with multiple firms. Nutshell's Person record has a single primary Company link. We migrate the most-recently-modified or most-active company association as the primary Company in Nutshell and store additional company associations in a custom field (Related_Companies__c) as a comma-separated list for reference. This is a known limitation of the destination model — your team may need to manually review contacts with multiple active firm relationships to determine whether additional Nutshell Person records are warranted.

  • Time tracking migrates as reference records, not billable invoices

    Time Matters has deep time-tracking and billing integration where billable hours, expense entries, and trust balances are first-class data. Nutshell does not have a native billing or invoicing module — time entries migrate as Nutshell Tasks with custom fields capturing hours and expense data, and trust balance snapshots are stored as one-time values on the associated Deal. The billable-hour data is preserved for reference and reporting in Nutshell but cannot generate invoices or process payments natively. Firms that rely on Time Matters' billing features need a separate billing or accounting tool post-migration.

  • Workflows, templates, and automated rules do not migrate

    Time Matters firms typically have custom workflows, document templates, merge templates, and automated triggers built over years of use. These are configuration artifacts that do not have a direct equivalent in Nutshell and cannot be migrated as data. We export Time Matters workflow definitions and template metadata as a rebuild reference document that your Nutshell administrator can use to recreate automation logic in Nutshell's automation tools. The export includes trigger conditions, action sequences, and template field mappings in a structured format.

Migration approach

Six steps for a successful Time Matters(r) to Nutshell data migration

  1. Extract and inventory the Time Matters schema

    FlitStack AI connects to the Time Matters SQL Server database using administrator credentials or processes custom export templates generated from the Time Matters client. We extract the full field inventory across all record types, identify active versus unused custom fields, and document the relationship graph between Contacts, Matters, Companies, Events, and Tasks. This inventory is reviewed with your team to confirm which fields should migrate, which should be pruned, and which matter types map to Nutshell Deals with which custom field assignments.

  2. Create Nutshell custom fields and configure the schema

    Before data loads, FlitStack AI creates the Nutshell custom fields needed for your migrated Time Matters data using Nutshell's custom field API. This includes practice area pick-lists on Deals, matter-number text fields, hours and expense custom fields on Tasks, and any other Time Matters fields that lack a native Nutshell equivalent. We also configure the Nutshell pipeline stages to map to your most common Matter statuses so the Deal stage values reflect your firm's workflow.

  3. Resolve owners and user mapping

    Time Matters users and responsible attorneys are matched to Nutshell users by email address. FlitStack AI generates a user mapping spreadsheet that your administrator reviews and confirms. Unmatched Time Matters owners — those without a corresponding Nutshell user account — are flagged and assigned to a fallback Nutshell user or left unassigned for manual assignment after migration. No record is loaded without a confirmed owner mapping or documented fallback.

  4. Run a sample migration with field-level diff

    A representative slice of records — typically 100–500 covering contacts from multiple attorneys, companies, matters of different types, and a range of activity records — migrates first. FlitStack AI generates a field-level diff report comparing source values to destination values for every mapped field. Your team reviews the sample to verify matter-number mapping, practice area assignment, owner resolution, and time entry preservation before the full run is committed.

  5. Execute full migration with delta-pickup window

    The full migration loads all contacts, companies, matters, events, tasks, notes, time entries, expense entries, and file attachments into Nutshell via the JSON-RPC API. A delta-pickup window of 24–48 hours runs concurrently, capturing any records created or modified in Time Matters during the cutover period. FlitStack AI maintains scoped read access to Time Matters throughout the migration window so your team can continue working in Time Matters without interruption until the go-live switch.

  6. Audit, validate, and hand off rebuild references

    Post-migration, FlitStack AI delivers a complete audit log of every record loaded — source ID, destination ID, load timestamp, and any warnings or skips. Your team runs a reconciliation check against Time Matters record counts and key field values. We also deliver the workflow definitions and template export as a structured rebuild reference for your Nutshell administrator to use when recreating automation logic. One-click rollback is available for 72 hours after go-live if reconciliation identifies systematic issues requiring a restart.

Platform deep dives

Context on both ends of the pair

Time Matters(r) logo

Time Matters(r)

Source

Strengths

  • True relational database architecture with many-to-many Contact-Matter relationships
  • Deep merge-template system with field-level control for document assembly workflows
  • Fully customizable field names, form layouts, and practice-area sort tabs
  • Flat-rate pricing with no per-user billing surprises
  • Long-standing product with a stable file format and export infrastructure

Weaknesses

  • No public API — all data movement is manual file-based export
  • Desktop-client-only (on-premises) with no native cloud or mobile access
  • UI and feature set lag behind modern cloud-native legal platforms
  • Low customer satisfaction scores relative to alternatives on G2 and Capterra
  • Billing and accounting modules considered cumbersome by experienced users
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 Time Matters(r) 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

    Time Matters(r): Not applicable.

  • Data volume sensitivity

    B

    Time Matters(r) doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Time Matters(r) 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 Time Matters(r) to Nutshell data migrations

Answers to the questions buyers ask most during Time Matters(r) to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Time Matters(r) to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most Time Matters to Nutshell migrations complete within 48–72 hours of clock time for under 50,000 total records. Larger firms with 500,000+ records or complex custom field schemas extending beyond 100 active fields extend to 5–7 days. The longest planning step is the custom field inventory and pruning review with your team — the actual data load runs in hours once the schema is confirmed. Nutshell's JSON-RPC API processes records in batches, and the API rate limits are respected throughout the migration run.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Time Matters(r).
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