Migrate from Time Matters(r) to Microsoft Dynamics 365 Sales

Time Matters contacts map 1:1 to Dynamics 365 Contacts. The Name, Email, Phone, Address, and Company fields map directly. Time Matters stores company as a text field on the contact record — we resolve it to an Account lookup by domain match or firm-name similarity before loading so the Contact.AccountId foreign key resolves correctly.

Time Matters Matters are legal cases. Dynamics 365 has no native Matter entity, so Matters map to Opportunities. The Matter name becomes the Opportunity Name; estimated billing and billable hours map to product line items on the Opportunity. Custom fields on the Matter form become Dataverse custom columns on the Opportunity table. Pipeline stages map to the default Dynamics 365 Sales Process unless a custom Business Process Flow is configured.

Time Matters supports N:N contact-matter associations natively. Dynamics 365 flattens this: the primary Contact gets the OpportunityContactRole on the Opportunity; additional contacts link to the parent Account via AccountContactRelationship. We identify the primary contact by the Matter's primary-contact flag or most-recent-modification rule, create the OpportunityContactRole, and surface the secondary contacts for AccountContactRelationship population in the migration plan.

Time Matters uses a single Events record type for calls, meetings, tasks, and notes — the record type is indicated by an internal type field in the export. We split each Events record into the appropriate Dynamics 365 activity entity (PhoneCall for calls, Appointment for meetings, Task for generic events) using the type field as the routing key. The original timestamp and assigned attorney owner are preserved on each new activity record.

Time Matters notes with free-form text and optional document attachments map to Dynamics 365 Annotations (the Dataverse note entity). Rich-text formatting in Time Matters notes is preserved as plain text if no HTML encoding is present. Document attachments on notes are re-uploaded to SharePoint and linked via the RegardingId on the Annotation record.

Time Matters time entries track billable hours, billing rate, and attorney name per Matter. We map each time entry to a product line item on the parent Opportunity, using the billing rate as the unit price and hours as quantity. The attorney name becomes a custom field on the product line item. Time entries that cannot be cleanly mapped to a product structure are preserved as Notes on the Opportunity with a Time_Entry__c prefix.

Time Matters documents attached to Matters or Contacts are re-hosted in SharePoint Online and linked back to the parent record via the RegardingId on the SharePoint Document Location entity. The original file name and upload timestamp are preserved as metadata. Inline images embedded in Time Matters notes are downloaded and attached to the corresponding Annotation record.

Time Matters merge templates encode field names and merge syntax in a proprietary format. Dynamics 365 does not have a template inbox that accepts this encoding. We export merge templates as reference PDF or Word files so your Dynamics 365 admin can rebuild them in Power Automate with Dataverse field references — the logic is preserved for rebuild but cannot be imported automatically.

Time Matters assigns internal numeric IDs to each record. We store these on a Source_System_ID__c custom column on every target entity so delta runs can de-duplicate records that may have been created in both systems during the cutover window, and so FlitStack's audit log references the original Time Matters record on every operation.

Time Matters allows unlimited custom fields defined per-form with no centralized schema catalog. We scan all export CSV headers across every export template to collect every unique custom field name, infer the data type from the first non-null value in each column, and create a corresponding Dataverse column (new_fieldname) in a FlitStack migration solution before the data load runs. Custom pick-list fields require a value-mapping table to map Time Matters codes to Dataverse option-set integer values.