Migrate your Time Matters(r) data
Desktop-first legal practice management with deep merge-template and relational data capabilities, now showing its age against cloud-native alternatives.
In its favor
Why people choose Time Matters(r)
The signal that keeps Time Matters(r) on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
The merge-into-templates feature is still unmatched for firms with large form libraries — one long-time user since 1998 calls it the best relational-database merge processing available in any legal CRM.
The many-to-many relationship between Contacts and Matters lets firms link a single contact to multiple cases without duplicating records, which modern flat CRMs often lose in migration.
Firms value deep field-name and visual-record-form customization, allowing the software to match idiosyncratic firm workflows without code changes.
The flat-rate pricing model appeals to solo and small firms that want predictable monthly costs with no per-user surprises.
Long-established users cite the separate contact and matter databases and the sort-select tab organization by practice area as the core reason they stayed for years.
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.
Reasons to switch
Why people leave Time Matters(r)
The recurring reasons buyers give for replacing Time Matters(r). Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Time Matters(r) fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Time Matters(r) pricing overview
Time Matters is priced at a flat rate of $39 per month according to Capterra, with no per-user breakdown visible in current public listings. This pricing model is simpler than per-seat competitors but reflects that the product is desktop-only and lacks the per-user licensing tiers common in cloud legal platforms.
Standard
Tier 1 of 1
$39/user/month (flat rate reported by Capterra)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Time Matters(r)'s schedule — see our quote-based pricing →
What gets migrated
Time Matters(r) object support
Object-by-object support for Time Matters(r) migrations. Per-pair details surface during scoping.
Contacts
Fully supportedTime Matters maintains a separate contact database with many-to-many relationships to Matters. We export via Custom Export, select all fields, include archived records, and map each contact's unique ID to preserve relationships in the destination CRM.
Matters
Fully supportedMatters (cases) are the core record type alongside Contacts, Events, and ToDos. We export Matters with all standard fields, custom form fields, and the Matter-Contact linkage table to reconstruct relationships in the destination.
Events
Fully supportedEvents (calendar entries) are one of the four main record types in Time Matters. We export via the same Custom Export wizard, selecting the Events record type and preserving date, time, and linked Matter associations.
ToDo's (Tasks)
Fully supportedTasks are exported as a distinct record type using the Custom Export wizard. We preserve due dates, completion status, priority flags, and the task-to-Matter linkage.
Notes
Fully supportedNotes are exported as a standalone record type, preserving rich text content, creation dates, and links to the parent Contact or Matter. We map note body fields directly to the destination's note or document object.
Time and Expenses
Mapping requiredTime and expense records export via the Custom Export wizard but require careful mapping of billing codes, rates, and date formats. We cross-reference with billing module data to ensure billable hours and expense amounts land correctly in the destination practice management system.
Custom Forms and Fields
Mapping requiredTime Matters allows customizable field names and custom visual record forms. When exporting, we identify every non-standard field, build a field map, and either create matching custom fields in the destination or flag where values must be collapsed into standard fields.
Document Attachments
Not in this platformTime Matters stores documents and PDFs linked to matters, but the export wizard does not include binary file attachments. We extract document metadata (filename, path, date, linked matter) and flag that a separate file share migration is required for the actual document library.
Billing and Accounting Records
Mapping requiredTime Matters has integrated billing and accounting features. Exporting invoice history, trust account balances, and ledger entries requires running multiple exports and cross-referencing by Matter number. We separate AR/AP open balances from historical transaction history since they map to different objects in destination platforms.
TM Messenger / Internal Communications
Not in this platformTM Messenger logs and internal communications stored within Time Matters are not included in the standard export. We do not migrate these records and flag them for the customer as a separate data consideration.
Merge Templates
Mapping requiredFirms often have hundreds of HotDocs-style merge templates stored in Time Matters. We export the template library as a file share, record the template-to-field mappings, and document the template list so it can be rebuilt in the destination document assembly system.
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Time Matters maintains a separate contact database with many-to-many relationships to Matters. We export via Custom Export, select all fields, include archived records, and map each contact's unique ID to preserve relationships in the destination CRM. |
| Matters | Fully supported | Matters (cases) are the core record type alongside Contacts, Events, and ToDos. We export Matters with all standard fields, custom form fields, and the Matter-Contact linkage table to reconstruct relationships in the destination. |
| Events | Fully supported | Events (calendar entries) are one of the four main record types in Time Matters. We export via the same Custom Export wizard, selecting the Events record type and preserving date, time, and linked Matter associations. |
| ToDo's (Tasks) | Fully supported | Tasks are exported as a distinct record type using the Custom Export wizard. We preserve due dates, completion status, priority flags, and the task-to-Matter linkage. |
| Notes | Fully supported | Notes are exported as a standalone record type, preserving rich text content, creation dates, and links to the parent Contact or Matter. We map note body fields directly to the destination's note or document object. |
| Time and Expenses | Mapping required | Time and expense records export via the Custom Export wizard but require careful mapping of billing codes, rates, and date formats. We cross-reference with billing module data to ensure billable hours and expense amounts land correctly in the destination practice management system. |
| Custom Forms and Fields | Mapping required | Time Matters allows customizable field names and custom visual record forms. When exporting, we identify every non-standard field, build a field map, and either create matching custom fields in the destination or flag where values must be collapsed into standard fields. |
| Document Attachments | Not in this platform | Time Matters stores documents and PDFs linked to matters, but the export wizard does not include binary file attachments. We extract document metadata (filename, path, date, linked matter) and flag that a separate file share migration is required for the actual document library. |
| Billing and Accounting Records | Mapping required | Time Matters has integrated billing and accounting features. Exporting invoice history, trust account balances, and ledger entries requires running multiple exports and cross-referencing by Matter number. We separate AR/AP open balances from historical transaction history since they map to different objects in destination platforms. |
| TM Messenger / Internal Communications | Not in this platform | TM Messenger logs and internal communications stored within Time Matters are not included in the standard export. We do not migrate these records and flag them for the customer as a separate data consideration. |
| Merge Templates | Mapping required | Firms often have hundreds of HotDocs-style merge templates stored in Time Matters. We export the template library as a file share, record the template-to-field mappings, and document the template list so it can be rebuilt in the destination document assembly system. |
Gotchas
What to watch for in Time Matters(r) migrations
Issues we've hit on past Time Matters(r) migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving Time Matters(r)?
Where Time Matters(r) customers move next
12 destinations Time Matters(r) can migrate to.
How a Time Matters(r) migration works
Four steps, Time Matters(r)-specific
Connect
None — no public API into Time Matters(r). Scopes limited to read-only on the data we move.
Map
We translate Time Matters(r)-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Time Matters(r) quirks before production.
Migrate
Full migration with Time Matters(r) rate-limit handling. Rollback available throughout.
FAQ
Time Matters(r) migration FAQ
Answers to the questions buyers ask most during Time Matters(r) migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Time Matters(r) migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Time Matters(r).
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Time Matters(r) setup and destination — written quote back within a business day.