CRM migration
Field-level mapping, validation, and rollback between Time Matters(r) and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Time Matters(r)
Source
Freshsales
Destination
Compatibility
10 of 10
objects map 1:1 between Time Matters(r) and Freshsales.
Complexity
BStandard
Timeline
2–4 weeks
Overview
Time Matters® is a desktop legal practice-management system that stores contacts, matters (cases), events, tasks, notes, time entries, and custom form data in a local database. It has no API — migrations run through its custom export-template system, producing CSV files that must then be imported into Freshsales. Freshsales is a cloud CRM with standard objects for contacts, accounts (called Accounts), deals (called Deals), tasks, meetings, and notes. Its Enterprise plan adds custom modules, which is where Time Matters custom-form fields land. The migration must resolve Time Matters staff records to Freshsales users by email, map Time Matters matter status and practice-area fields to Freshsales account custom fields, flatten Time Matters' N:N contact-to-matter relationships into a primary deal association, and carry time/expense data into Freshsales custom fields or a custom module. Automations, billing invoices, and document templates do not migrate — those require manual rebuild in Freshsales or a separate billing workflow.
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 Freshsales, 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
Freshsales
Contact
1:1Time Matters contacts map directly to Freshsales contacts. Freshsales enforces a unique, valid email address per contact record — contacts without emails are flagged for manual review before the import run. Duplicate email addresses collapse to a single Freshsales contact.
Time Matters(r)
Matter
Freshsales
Account
1:1Time Matters matters (legal cases) translate to Freshsales accounts because both represent a client-level entity with multiple associated contacts, notes, and activities. The matter name becomes the account name; the case number and status migrate as custom fields. If the firm tracks deals within matters, those become Freshsales Deals linked to the account.
Time Matters(r)
Matter
Freshsales
Deal
1:1If the firm uses Time Matters to track billable matters with revenue or budget values, those translate to Freshsales Deals with the amount in the standard Amount field. Matter status maps to Deal stage. Each matter-to-deal translation is planned per matter-type to handle flat-rate vs. hourly billing structures.
Time Matters(r)
Matter-Custom Forms
Freshsales
Custom Fields / Custom Modules
1:1Time Matters custom form fields (practice-area-specific data capture) have no direct Freshsales equivalent. Each custom form field becomes either a custom field on the Contact or Account object, or a custom module (Freshsales Enterprise) for complex multi-field forms. We plan this mapping during the schema review phase before import.
Time Matters(r)
Event
Freshsales
Sales Activity (Call / Meeting)
1:1Time Matters events (calendar entries, appointments, hearings, depositions) map to Freshsales Meetings. Events with Type=Call map to Freshsales Calls. The original event date/time, duration, and associated matter (now Account) are preserved as linked fields. Events without a specific time are imported as tasks.
Time Matters(r)
ToDo
Freshsales
Task
1:1Time Matters to-do items map to Freshsales tasks. The due date, priority flag, and completion status translate directly. Open to-dos import as open Freshsales tasks; completed to-dos import with a completed date. Tasks are linked to the relevant Contact or Account record.
Time Matters(r)
Note
Freshsales
Note
1:1Time Matters notes migrate as Freshsales notes. The note body text, author (mapped to Freshsales user), and original creation timestamp are preserved. Notes are linked to the Contact or Account they were attached to in Time Matters. Rich-text formatting in Time Matters notes may require plain-text normalization.
Time Matters(r)
Time Entry
Freshsales
Custom Fields / Custom Module
1:1Time Matters stores billable time entries, expenses, and trust accounting data that has no equivalent in Freshsales. These migrate as custom fields on the Account or Deal object, or into a custom module on the Enterprise plan. Firms requiring detailed billing reporting need a separate billing tool or a rebuild in Freshsales.
Time Matters(r)
Staff / User
Freshsales
User
1:1Time Matters staff records are resolved to Freshsales users by email address match. Unmatched staff (no Freshsales user with a matching email) are flagged before migration — the team either creates Freshsales users first or assigns their records to a fallback user. This is required before deals and activities can map to owners.
Time Matters(r)
Attachment / Document
Freshsales
File
1:1Time Matters file attachments and documents linked to contacts, matters, or notes are downloaded and re-uploaded to Freshsales as files attached to the corresponding record. File size limits in Freshsales (100GB/user on Enterprise) apply. Inline images in notes are downloaded and re-hosted.
| Time Matters(r) | Freshsales | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Matter | Account1:1 | Fully supported | |
| Matter | Deal1:1 | Fully supported | |
| Matter-Custom Forms | Custom Fields / Custom Modules1:1 | Fully supported | |
| Event | Sales Activity (Call / Meeting)1:1 | Fully supported | |
| ToDo | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Time Entry | Custom Fields / Custom Module1:1 | Fully supported | |
| Staff / User | User1:1 | Fully supported | |
| Attachment / Document | File1: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
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Review Time Matters export templates and validate field coverage
FlitStack reviews the Time Matters custom export templates configured in the desktop client to confirm which record types and fields are available for export. We identify any custom form fields not included in the current export template and recommend template modifications before the export runs. We also run a data-quality audit: missing emails, duplicate contact records, inactive matters, and incomplete time entries are flagged with counts so the firm can decide on cleanup before migration.
Create Freshsales custom fields and custom modules for Time Matters data
FlitStack delivers a custom field creation plan listing every Time Matters field that has no direct Freshsales equivalent — practice area, billing rate, engagement rating, matter status, and all custom form fields. The firm's Freshsales admin creates these fields in Admin Settings before the migration import. We provide exact field names, data types, and pick-list values from the Time Matters export so the admin can configure them without guessing.
Resolve Time Matters staff to Freshsales users by email
Time Matters staff records are matched to Freshsales users by email address. FlitStack generates an owner-resolution report listing every Time Matters staff member, their email, and the corresponding Freshsales user status. Staff without a matching Freshworks user are flagged — the firm creates those users before migration, or their records are assigned to a designated fallback Freshsales user. No deal, task, or activity can map to an owner until this resolution is complete.
Run sample migration with field-level diff
A representative slice of Time Matters data — typically 100–500 records spanning contacts, matters, events, to-dos, and notes — is exported and imported into a Freshsales sandbox or trial account. FlitStack generates a field-level diff comparing the exported values against the imported Freshsales records. The firm reviews matter-to-account mapping, contact-email duplicates, billing custom field placement, and owner resolution before the full migration run commits.
Execute full migration with delta-pickup window
The full Time Matters dataset is exported via the validated custom export templates and imported into Freshsales via the import API, with field mapping applied per the migration plan. After the initial import completes, a delta-pickup window (24–48 hours) captures any records created or modified in Time Matters during the cutover. An audit log records every import operation, and one-click rollback is available if reconciliation identifies data discrepancies.
Platform deep dives
Time Matters(r)
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 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 Freshsales.
Object compatibility
2 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 Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Time Matters(r) to Freshsales 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 Freshsales
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.