CRM migration
Field-level mapping, validation, and rollback between InfoTrack and Microsoft Dynamics 365 Sales . We move data and schema; workflows are rebuilt natively in Microsoft Dynamics 365 Sales .
InfoTrack
Source
Microsoft Dynamics 365 Sales
Destination
Compatibility
9 of 10
objects map 1:1 between InfoTrack and Microsoft Dynamics 365 Sales .
Complexity
BStandard
Timeline
3–6 weeks
Overview
InfoTrack is a litigation workflow platform — not a traditional CRM — so the migration to Dynamics 365 Sales requires a domain translation rather than a direct object map. InfoTrack stores matters, service orders, court-docket records, party information, and integration links to practice-management systems. Dynamics 365 Sales uses the Common Data Model (Dataverse) with Accounts, Contacts, Leads, Opportunities, Quotes, Orders, and custom entities. FlitStack AI maps InfoTrack matters to Opportunities or custom matter entities, parties to Account/Contact records with their roles preserved, and service-order history to Order records or custom service-history entities. The eFiling, process-serving, and docket-sync workflows that drive InfoTrack's value have no Dynamics 365 Sales equivalent — we export configuration definitions so your team can rebuild them in Power Automate or Dynamics workflows post-migration. We use Dynamics 365's Web API (Dataverse) for the data layer, with Bulk API for high-volume record loads and field-level diff validation before commit.
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.
Source platform
InfoTrack platform overview
Scorecard, SWOT, gotchas, and pricing for InfoTrack.
Destination platform
Microsoft Dynamics 365 Sales platform overview
Scorecard, SWOT, gotchas, and pricing for Microsoft Dynamics 365 Sales .
Data migration guide
The complete Microsoft Dynamics 365 Sales migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Microsoft Dynamics 365 Sales migration checklist
Pre- and post-cutover tasks for moving onto Microsoft Dynamics 365 Sales .
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a InfoTrack object lands in Microsoft Dynamics 365 Sales , including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
InfoTrack
Matter / Case
Microsoft Dynamics 365 Sales
Opportunity or Custom Matter Entity
1:1InfoTrack matters do not map directly to any single Dynamics 365 Sales object. We evaluate matter type (litigation, transactional, advisory) and map each to either a standard Opportunity (for matters with revenue) or a custom Matter table created in Dynamics 365 Dataverse. Custom Matter entity stores matter type, court jurisdiction, judge assignment, and status — this is the primary record in the new CRM.
InfoTrack
Party (Plaintiff / Defendant / Opposing Counsel)
Microsoft Dynamics 365 Sales
Account + Contact
many:1InfoTrack party records — including client, opposing party, and counsel contacts — merge into Dynamics 365 Account and Contact objects. Each party type gets a Role field on the Account or Contact record to preserve the legal relationship. Multiple parties on one matter use Account Contact Roles on the related Opportunity or custom Matter entity.
InfoTrack
Service Order (eFiling / Process Serving / Search)
Microsoft Dynamics 365 Sales
Order or Custom Service Record Entity
1:1InfoTrack service orders (eFiling submissions, process-serving requests, court searches) translate to Dynamics 365 Sales Order records for structured orders or a custom Service_History__c entity for detailed service metadata. Service type, court, filing date, and order status map to corresponding fields or custom fields on the entity.
InfoTrack
Court / Jurisdiction
Microsoft Dynamics 365 Sales
Custom Court_Jurisdiction__c Entity
1:1Dynamics 365 Sales has no native court or jurisdiction entity. We create a Court_Jurisdiction__c custom table in Dataverse with fields for court name, state, federal/bankruptcy designation, and eFiling system URL. InfoTrack matter records link to this entity via a lookup field.
InfoTrack
Document / Filing (PDF orders, court returns)
Microsoft Dynamics 365 Sales
SharePoint + Note/Attachment
1:1InfoTrack documents and court-returned filings are downloaded and uploaded to Dynamics 365 Sales' native SharePoint document management (enabled via Microsoft 365 integration). Documents attach to the related Account, Contact, or custom Matter entity. Original filenames and filing dates are preserved in SharePoint metadata.
InfoTrack
Docket Entry / Calendar Event
Microsoft Dynamics 365 Sales
Activity (Appointment / Task)
1:1InfoTrack docket-sync entries and court-date reminders map to Dynamics 365 Sales Activities — appointments for court hearings and tasks for filing deadlines. Original court dates and judge names become subject and description fields. The related Matter or Account links via the regarding object.
InfoTrack
Invoice / Billing Record
Microsoft Dynamics 365 Sales
Invoice
1:1InfoTrack invoices exported as CSV map to Dynamics 365 Sales Invoice records. Invoice number, date, amount, and client reference carry forward. InfoTrack's pay-per-use billing history becomes a financial reference record on the Account — billable expense tracking is handled separately in Dynamics 365 Finance or an accounting integration.
InfoTrack
Practice-Management Integration Link
Microsoft Dynamics 365 Sales
No Equivalent — Custom Reference Field
1:1InfoTrack's integration links to Time Matters, LEAP, and Clio have no Dynamics 365 Sales equivalent. We preserve integration endpoint URLs and system names in a custom text field (Source_Integration__c) for reference. Rebuilding integrations with practice-management systems requires a separate implementation project using Dynamics 365's API or a middleware connector.
InfoTrack
User / Attorney Owner
Microsoft Dynamics 365 Sales
User
1:1InfoTrack user and attorney records resolve to Dynamics 365 Sales User accounts via email match. Unmatched owners are flagged before migration — your team either creates Dynamics users first or assigns records to a fallback user. Active/inactive status carries forward.
InfoTrack
Custom Matter Properties
Microsoft Dynamics 365 Sales
Custom Fields on Matter Entity
1:1InfoTrack custom fields on matter records (case type codes, statutory references, litigation hold flags) require custom fields on the custom Matter entity in Dataverse. Field data types are preserved — pick-list values are rebuilt as Dataverse option sets, date fields as datetime fields.
| InfoTrack | Microsoft Dynamics 365 Sales | Compatibility | |
|---|---|---|---|
| Matter / Case | Opportunity or Custom Matter Entity1:1 | Fully supported | |
| Party (Plaintiff / Defendant / Opposing Counsel) | Account + Contactmany:1 | Fully supported | |
| Service Order (eFiling / Process Serving / Search) | Order or Custom Service Record Entity1:1 | Fully supported | |
| Court / Jurisdiction | Custom Court_Jurisdiction__c Entity1:1 | Fully supported | |
| Document / Filing (PDF orders, court returns) | SharePoint + Note/Attachment1:1 | Fully supported | |
| Docket Entry / Calendar Event | Activity (Appointment / Task)1:1 | Fully supported | |
| Invoice / Billing Record | Invoice1:1 | Fully supported | |
| Practice-Management Integration Link | No Equivalent — Custom Reference Field1:1 | Fully supported | |
| User / Attorney Owner | User1:1 | Fully supported | |
| Custom Matter Properties | Custom Fields on Matter Entity1: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.
InfoTrack gotchas
InfoTrack is a workflow layer with no standalone CRM data model
Custom folder sync for documents requires Time Matters 16.6+
No public API means bulk export requires manual CSV downloads
Integration keys must be regenerated when reconnecting to a new case management system
Per-order invoice granularity complicates matter-level billing reconstruction
Microsoft Dynamics 365 Sales gotchas
Professional tier 15-table custom table limit blocks migrations
October 2024 pricing increase applies at renewal for all customers
Custom fields must be created in the UI before API writes
Power Platform request limits apply to bulk migrations
Activity records orphaned to inactive owners fail silently
Pair-specific challenges
Migration approach
Discovery and schema planning
We audit InfoTrack matter records, party records, service orders, document inventory, and docket entries. We map each to either a standard Dynamics 365 Sales object (Account, Contact, Opportunity, Order) or a custom Matter entity in Dataverse. If your InfoTrack setup uses custom matter fields, we document field types and pick-list values for Dataverse custom-field creation. We also confirm your Dynamics 365 license tier (Professional vs. Enterprise) to validate custom-table allowance and SharePoint document management availability.
Create Dynamics 365 custom entities and fields
We provision the custom Court_Jurisdiction__c and Matter__c entities in Dataverse, along with all required custom fields (Matter_Type__c, Filing_Status__c, Judge_Name__c, Source_Integration__c, Original_Create_Date__c, InfoTrack_Matter_ID__c). We configure option-set values for pick-list fields matching InfoTrack's legal-domain values. This step runs in a Dynamics 365 sandbox environment first; production deployment happens after field-level diff validation. We also verify field-level security roles and Power Automate triggers that will reference these entities, ensuring downstream workflows are prepared for the new schema.
Resolve InfoTrack users to Dynamics 365 users by email
We extract all InfoTrack attorney and staff owner records and match them against existing Dynamics 365 Sales users by email address. Unmatched owners are flagged in a pre-migration report — your team either creates corresponding Dynamics users or designates a fallback user for records without a match. No record migrates without a resolved OwnerId in Dynamics 365. This mapping ensures accurate ownership tracking and audit compliance across all migrated matters.
Run sample migration with field-level diff
A representative slice of 100–500 records migrates first — spanning matters across different types, parties with various roles, service orders with mixed statuses, and a sample of docket entries and documents. We generate a field-level diff report comparing source values against destination field values. You verify matter-type mapping, party-role assignment, order status translation, and document linkage before the full run commits.
Execute full migration with delta-pickup
The full dataset loads into Dynamics 365 Sales using Dataverse Bulk API for high-volume batches. A delta-pickup window (24–48 hours) captures any new InfoTrack service orders or docket entries created during the cutover window. SharePoint documents upload in parallel with record migration. Audit log captures every operation; one-click rollback reverts all changes if reconciliation fails. We also perform a final validation pass to confirm that all relationships (Account, Contact, Opportunity) are correctly linked before sign-off.
Platform deep dives
InfoTrack
Source
Strengths
Weaknesses
Microsoft Dynamics 365 Sales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 of 8 objects need a manual workaround.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across InfoTrack and Microsoft Dynamics 365 Sales .
Object compatibility
1 of 8 objects need a manual workaround.
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
InfoTrack: Not publicly documented.
Data volume sensitivity
InfoTrack 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 InfoTrack to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.
Walk through your InfoTrack to Microsoft Dynamics 365 Sales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave InfoTrack
Other ways to arrive at Microsoft Dynamics 365 Sales
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.