CRM migration

Migrate from Time Matters(r) to Salesforce Sales Cloud

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

Time Matters(r) logo

Time Matters(r)

Source

Salesforce Sales Cloud

Destination

Salesforce Sales Cloud logo

Compatibility

100%

12 of 12

objects map 1:1 between Time Matters(r) and Salesforce Sales Cloud.

Complexity

BStandard

Timeline

4–8 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Time Matters is a legal practice management system built around four core record types: Contacts, Matters, Events, and Tasks, with a relational database supporting many-to-many links between contacts and matters. Firms rely on it for calendaring, document merge templates, trust accounting, and matter-centric billing. The platform predates modern cloud architecture — it stores data in local .tmd files and exports via custom templates to CSV, with no native API for real-time integration. Salesforce Sales Cloud uses a standard object model (Account, Contact, Case, Task, Event) with a different relational paradigm: contacts require an AccountId lookup, and multi-entity relationships need junction objects. FlitStack AI extracts Time Matters data via the platform's built-in Custom Export wizard, maps the N-to-N contact-matter graph to a Contact_Matter_Junction__c custom object, translates billing time entries to custom Expense__c and TimeEntry__c records, and loads everything through Salesforce Bulk API with a field-level diff before commit. Workflows, document merge templates, and trust-accounting rules do not migrate — they require manual rebuild in Salesforce Flow, DocuSign, and Financial Services Cloud respectively.

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

Salesforce Sales Cloud logo

Salesforce Sales Cloud

What's pulling them in

  • The AppExchange marketplace with 5,000+ prebuilt apps gives enterprises integrations for nearly every business workflow without custom development.
  • Native Einstein AI for lead scoring, opportunity insights, and predictive forecasting adds intelligence without a separate platform purchase.
  • Territory management, multi-currency support, and advanced forecasting satisfy the needs of complex B2B sales organizations with structured revenue teams.
  • Slack, Tableau, and CPQ are deeply integrated into the core platform, keeping the sales stack unified for teams already in the Salesforce ecosystem.
  • Organizations with a large, established Salesforce implementation choose it because switching costs — integrations, custom code, trained admins — are prohibitive.

Object mapping

How Time Matters(r) objects map to Salesforce Sales Cloud

Each row shows how a Time Matters(r) object lands in Salesforce Sales Cloud, 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

Salesforce Sales Cloud

Contact

1:1
Fully supported

Time Matters Contact records map directly to Salesforce Contact. The AccountId lookup requires that the firm (for attorney contacts) or client organization (for matter contacts) is loaded first. Unmatched firm names create a default 'Firm Unassigned' Account. Time Matters contact-type flags (Client, Opposing Counsel, Vendor) become custom pick-list values on a Contact_Type__c custom field.

Time Matters(r)

Firm (organization)

maps to

Salesforce Sales Cloud

Account

1:1
Fully supported

Time Matters stores firm and organization names alongside contacts. These map to Salesforce Account records. Law firm name, office address, and bar number fields from Time Matters become custom fields on the Account object (Firm_Name__c, Bar_Number__c). Multi-office firms where Time Matters stores one record per office collapse to one Account with multiple Account Contact Relations.

Time Matters(r)

Matter

maps to

Salesforce Sales Cloud

Matter__c (custom object)

1:1
Fully supported

Time Matters Matter records have no native Salesforce equivalent. FlitStack AI creates a custom Matter__c object in Salesforce with fields mirroring the source schema: Matter_Number__c, Matter_Title__c, Description__c, Status__c, Practice_Area__c, Responsible_Attorney__c, Client_Name__c, Open_Date__c, Close_Date__c, Billing_Method__c, Matter_Object_ID__c for traceability. The custom object is deployed via Salesforce Metadata API before data loading begins.

Time Matters(r)

MATTERCONTACT (N:N join)

maps to

Salesforce Sales Cloud

Contact_Matter_Junction__c (junction object)

1:1
Fully supported

Time Matters allows a contact to link to N matters and a matter to have N contacts via the MATTERCONTACT join table. This N-to-N relationship requires a custom junction object (Contact_Matter_Junction__c) with lookup fields to both Contact and Matter__c, plus a Role__c pick-list field preserving the Time Matters contact role on that matter. Loading requires both parent records to exist first — Matter__c and Contact — before the junction table loads.

Time Matters(r)

Event

maps to

Salesforce Sales Cloud

Event

1:1
Fully supported

Time Matters Events (calendar entries, depositions, hearings, filing deadlines) map to Salesforce Event records. The Subject, StartDateTime, EndDateTime, Description, and IsAllDayEvent fields carry over directly. Events linked to a Matter via MATTERCONTACT get the Matter__c lookup populated through the junction record. Original create timestamps and created-by users are preserved as custom fields (Original_Create_Date__c, Created_By_User__c).

Time Matters(r)

ToDo / Task

maps to

Salesforce Sales Cloud

Task

1:1
Fully supported

Time Matters ToDo records map to Salesforce Task. Subject, Status, Priority, ActivityDate (due date), and Description migrate directly. Open todos preserve their original created date in Original_Create_Date__c. Tasks linked to a matter carry the Matter__c lookup through the junction table. Completed vs. open status maps via a value-mapping table (Open=Not Started, Completed=Completed in Salesforce).

Time Matters(r)

Note

maps to

Salesforce Sales Cloud

Note

1:1
Fully supported

Time Matters Notes migrate as Salesforce Notes. The Note Title maps from Time Matters' subject or first-line text, and Body carries the full note content. Notes are linked to their parent Contact or Matter__c record by lookup. If Time Matters notes contain embedded file references, those references are stored as Note_Attachment_URL__c custom fields pointing to the re-uploaded Salesforce Files location.

Time Matters(r)

Document / File

maps to

Salesforce Sales Cloud

ContentDocument / Salesforce Files

1:1
Fully supported

Time Matters stores document paths and file references linked to matters and contacts. FlitStack AI extracts the referenced documents from the firm's file server (via the export), re-uploads them to Salesforce Files, and stores the ContentDocumentId and link URL in a Document_Reference__c field on the associated Matter__c or Contact record.

Time Matters(r)

Time Entry / Expense

maps to

Salesforce Sales Cloud

TimeEntry__c / Expense__c (custom objects)

1:1
Fully supported

Time Matters time and expense records track billable hours, rates, and expense amounts per matter. These have no Salesforce standard equivalent. FlitStack AI creates TimeEntry__c and Expense__c custom objects with fields: Entry_Date__c, Hours__c, Rate__c, Amount__c, Description__c, Billable__c, and a lookup to the associated Matter__c record. Default billing rates and invoice templates do not carry over.

Time Matters(r)

Billing / Invoice

maps to

Salesforce Sales Cloud

Invoice__c (custom object)

1:1
Fully supported

Time Matters generates invoices tied to matter billing entries. These map to a custom Invoice__c object with Invoice_Number__c, Invoice_Date__c, Total_Amount__c, Status__c, and a lookup to the associated Matter__c. Invoice templates and billing rules must be rebuilt in Salesforce CPQ or Financial Services Cloud after migration.

Time Matters(r)

Workflow / Automation Rule

maps to

Salesforce Sales Cloud

Flow / Process Builder

1:1
Fully supported

Time Matters workflow rules, internal triggers, task automation, and deadline-based alerts do not have a Salesforce equivalent and cannot be migrated. FlitStack AI exports the Time Matters workflow definitions as a reference document (PDF or Word) that your Salesforce admin can use to rebuild equivalent automation in Salesforce Flow or Apex triggers.

Time Matters(r)

Merge Template

maps to

Salesforce Sales Cloud

Salesforce Files + CPQ Document Generation

1:1
Fully supported

Time Matters document merge templates are stored as .dot or proprietary template files tied to specific matter types. These cannot be imported into Salesforce. FlitStack exports them as reference documents. Firms typically rebuild document generation using Salesforce CPQ, Conga Composer, or Drawloop after migration.

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

Salesforce Sales Cloud logo

Salesforce Sales Cloud gotchas

High

Workflow Rules and Process Builder are retired

High

Bulk API batch quota exhaustion during large imports

Medium

Storage overage billing is non-obvious

Medium

Account-Contact many-to-many relationship mapping

Low

Territory and team member import ordering dependencies

Pair-specific challenges

  • N-to-N contact-matter relationships require a custom junction table

    Time Matters stores contacts and matters in an N-to-N relationship via the MATTERCONTACT join table — a contact can appear on N matters, and a matter can have N contacts. Salesforce has no native N-to-N equivalent: contacts require a single primary AccountId, and matter links must use a custom junction object (Contact_Matter_Junction__c) with lookups to both Contact and Matter__c. FlitStack AI creates this junction table, but it must be deployed in Salesforce before data loads begin, and both the Matter__c and Contact parent records must exist before the junction rows insert. Failure to sequence this correctly causes referential integrity errors during loading.

  • Matters have no Salesforce standard object — a custom object must be created pre-migration

    Time Matters' core record is the Matter (case) — but Salesforce has no native Case object that maps cleanly to legal matters. Salesforce Case is designed for support tickets, not legal matters with billing rates, practice areas, responsible attorneys, and client-matter relationships. FlitStack AI must create a Matter__c custom object with all required custom fields (Matter_Number__c, Status__c, Practice_Area__c, Open_Date__c, Close_Date__c, Default_Rate__c, etc.) in your Salesforce org before any data can land. This schema creation step must complete and the object must be deployed before the migration tool can upsert matter records. Firms with 30+ custom matter fields will need additional setup time for pick-list value mapping and validation rules.

  • Trust-accounting and billing rules do not translate to Salesforce

    Time Matters includes trust-accounting ledgers, split-fee tracking, and matter-specific billing rules that are deeply embedded in the application's data model. Salesforce's standard objects have no equivalent trust-accounting schema — the closest native feature is Salesforce Financial Services Cloud, which requires a separate purchase and significant configuration. Time entries, expense records, and invoice references migrate as custom objects (TimeEntry__c, Expense__c, Invoice__c), but the billing calculations, trust ledger balances, and invoice templates do not. Firms should plan for a post-migration billing implementation project using Salesforce Financial Services Cloud, Conga, or a third-party legal billing integration.

  • Time Matters has no Salesforce-compatible API — all export is CSV-based

    Unlike modern SaaS platforms with REST APIs, Time Matters exports data exclusively via its built-in Custom Export wizard, which produces CSV files per record type. FlitStack AI must build a custom extraction pipeline that programmatically drives the Time Matters export wizard, downloads each CSV (Contacts, Matters, Events, Tasks, Notes, Time Entries), normalizes the column headers, and transforms the data for Salesforce Bulk API ingestion. This adds a step that cloud-to-cloud migrations do not require and extends discovery time by 3–5 days. Archived records must be exported separately using the 'Both' archived/non-archived toggle in the export wizard.

  • Workflows, automations, and merge templates require manual rebuild in Salesforce

    Time Matters workflow rules, task triggers, deadline-based alerts, and document merge templates are internal to Time Matters and have no Salesforce equivalent. Salesforce Flow, Process Builder, and Apex handle automation differently — they operate on Salesforce objects, not Matter__c custom objects by default. FlitStack AI exports the Time Matters workflow definitions as a reference PDF and documents the automation logic so your Salesforce admin can rebuild equivalent flows post-migration. This is a significant advisory effort that should be scoped separately from the data migration engagement.

Migration approach

Six steps for a successful Time Matters(r) to Salesforce Sales Cloud data migration

  1. Discovery and Time Matters export extraction

    FlitStack AI analyzes your Time Matters installation to identify all record types in use: Contacts, Matters, Events, Tasks, Notes, Time Entries, Expenses, and any custom fields defined in the system. We run the built-in Custom Export wizard for each record type, selecting 'Both' for archived/non-archived records to capture the full history. We extract the MATTERCONTACT join table separately to capture the N-to-N relationship graph. Data is validated for completeness (record counts per type, referential integrity between tables) before any transformation begins.

  2. Schema build and Salesforce custom object creation

    Before data can load, FlitStack AI creates the custom Matter__c object, the Contact_Matter_Junction__c junction object, and any custom fields needed for Time Matters data that has no standard Salesforce equivalent (Practice_Area__c, Default_Rate__c, TimeEntry__c, Expense__c, Invoice__c). We deploy these via Salesforce Metadata API into your sandbox first for validation. Once validated, the schema deploys to production. This step typically takes 3–5 business days and requires a Salesforce admin to approve the custom object deployment.

  3. Data transformation and field mapping

    FlitStack AI transforms the Time Matters CSV exports into Salesforce-compatible records. This includes: resolving firm names to AccountIds, mapping contact-type values to custom pick-list fields, translating Time Matters status values to Salesforce Task/Event status values, populating the Contact_Matter_Junction__c junction table with the N-to-N relationship rows, and writing original create/modified timestamps to custom datetime fields. The mapping is validated against the field_mapping specification before any load occurs.

  4. Sample migration with field-level diff

    A representative slice of records (typically 200–500 per object type) migrates into your Salesforce sandbox first. FlitStack AI generates a field-level diff comparing source and destination values side-by-side for every field in the mapping spec. You review the diff to confirm: matter status mapping, practice area values, contact-account resolution, junction table row completeness, and original timestamp preservation. Any mapping corrections are made before the full run commits.

  5. Full migration with delta-pickup cutover

    The full dataset loads into Salesforce production via Bulk API 2.0. A delta-pickup window (24–48 hours) runs concurrently with your Time Matters cutover: any records created or modified in Time Matters during the window are captured and loaded into Salesforce before go-live. An audit log records every upsert operation. FlitStack AI runs a post-load reconciliation comparing record counts and a spot-check of field values against the source CSV. One-click rollback is available if reconciliation reveals data integrity issues.

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
Salesforce Sales Cloud logo

Salesforce Sales Cloud

Destination

Strengths

  • Largest enterprise app ecosystem in CRM with 5,000+ AppExchange integrations covering nearly every vertical workflow.
  • Native Einstein AI delivers lead scoring, opportunity insights, and predictive forecasting without a third-party layer.
  • Advanced territory management, multi-currency, and flexible forecasting satisfy complex B2B revenue structures.
  • Deep platform extensibility: Custom Objects, Apex, Flow, and the Metadata API allow full schema customization.
  • Well-documented REST API, Bulk API, and Composite API with published rate limits for programmatic migration.

Weaknesses

  • Pricing model is layered and opaque in practice: per-seat fees plus storage overages, add-on subscriptions, and annual uplifts compound to 30–40% above sticker price.
  • Workflow Rules and Process Builder are deprecated, forcing all orgs onto Salesforce Flow — a migration task that catches many teams by surprise.
  • Steep administrative complexity: meaningful configuration requires a dedicated Salesforce admin or consultant.
  • API rate limits are edition-gated (100k/day base for Enterprise) and easily exhausted by large historical imports without throttling.
  • Data export is exportable via Data Loader but preserving relationship integrity across 30+ objects requires careful ETL sequencing.

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 Salesforce Sales Cloud.

  • 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 Salesforce Sales Cloud 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 Salesforce Sales Cloud data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most Time Matters to Salesforce migrations complete in 4–8 weeks from discovery to go-live for firms with under 25,000 records. The longest step is typically the custom object and junction table creation in Salesforce — those must deploy before data can load. Large firms with 100,000+ records or complex matter-billing schemas extend to 8–14 weeks. The actual data movement takes hours once the mapping and field-level diff are validated.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Time Matters(r).
Land in Salesforce Sales Cloud, 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