CRM migration
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)
Source
Nutshell
Destination
Compatibility
12 of 12
objects map 1:1 between Time Matters(r) and Nutshell.
Complexity
BStandard
Timeline
48–72 hours
Overview
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.
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 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
Nutshell
Person
1:1Time 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
Nutshell
Deal
1:1Time 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
Nutshell
Company
1:1Time 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
Nutshell
Activity
1:1Calendar 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
Nutshell
Task
1:1Time 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
Nutshell
Note
1:1Time 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
Nutshell
Task
1:1Time 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
Nutshell
Task
1:1Time 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
Nutshell
Activity / Note
1:1Time 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
Nutshell
Call
1:1Phone 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
Nutshell
File
1:1Time 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)
Nutshell
Custom Field
1:1Each 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.
| Time Matters(r) | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Event / Calendar Entry | Activity1:1 | Fully supported | |
| ToDo / Task | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Time Entry | Task1:1 | Fully supported | |
| Expense Entry | Task1:1 | Fully supported | |
| Email Communication | Activity / Note1:1 | Fully supported | |
| Phone Communication / Call Log | Call1:1 | Fully supported | |
| Document / Attachment | File1:1 | Fully supported | |
| Custom Fields (active) | Custom Field1: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.
Time Matters(r) gotchas
No API forces file-only migration with manual export wizard steps
Archived records excluded by default — explicit 'Both' selection required
Include field names checkbox is easy to miss, leaving CSVs headerless
Binary documents and attachments not included in any standard export
Merge template library requires separate file-share export, not in export wizard
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 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.
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.
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.
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.
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.
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
Time Matters(r)
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 Time Matters(r) 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
Time Matters(r): Not applicable.
Data volume sensitivity
Time Matters(r) 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 Time Matters(r) to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Time Matters(r)
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.