CRM migration

Migrate from InfoTrack to Microsoft Dynamics 365 Sales

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 logo

InfoTrack

Source

Microsoft Dynamics 365 Sales

Destination

Microsoft Dynamics 365 Sales  logo

Compatibility

90%

9 of 10

objects map 1:1 between InfoTrack and Microsoft Dynamics 365 Sales .

Complexity

BStandard

Timeline

3–6 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

InfoTrack logo

InfoTrack

What's pushing teams away

  • Court-stamped documents and expenses stop syncing back to the Matter when the eFiling service connection drops or the integration with the case management system expires, requiring manual re-authentication to resolve.
  • Credit card processing fees apply to every transaction, and ACH carries a state-variable flat fee that accumulates into a visible line item on invoices for high-volume litigation firms.
  • No public API means there is no programmatic way to extract bulk data from InfoTrack—all data retrieval requires manual CSV export from the admin UI, which limits what can be migrated to a new platform without vendor coordination.
  • Integration keys can be lost if the account admin closes the browser during onboarding, requiring a support request to regenerate the unique firm integration key for re-establishing the case management connection.

Choosing

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

What's pulling them in

  • Deep Microsoft 365, Teams, and Outlook integration makes Microsoft Dynamics 365 Sales a natural fit for Microsoft-first organizations already invested in that ecosystem
  • Sales Enterprise and Premium tiers offer unlimited custom tables and advanced AI-driven forecasting and predictive analytics not available in lower tiers
  • Professional tier pricing at $65 per user per month offers a lower entry cost than Salesforce for SMB teams with straightforward CRM needs
  • Flexible customization options allow businesses to build bespoke apps, tailor forms and views, and integrate with other Dynamics 365 modules
  • Microsoft Copilot AI tools are embedded directly into the sales workflow on Enterprise and Premium, automating routine tasks and providing deal intelligence

Object mapping

How InfoTrack objects map to Microsoft Dynamics 365 Sales

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

maps to

Microsoft Dynamics 365 Sales

Opportunity or Custom Matter Entity

1:1
Fully supported

InfoTrack 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)

maps to

Microsoft Dynamics 365 Sales

Account + Contact

many:1
Fully supported

InfoTrack 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)

maps to

Microsoft Dynamics 365 Sales

Order or Custom Service Record Entity

1:1
Fully supported

InfoTrack 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

maps to

Microsoft Dynamics 365 Sales

Custom Court_Jurisdiction__c Entity

1:1
Fully supported

Dynamics 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)

maps to

Microsoft Dynamics 365 Sales

SharePoint + Note/Attachment

1:1
Fully supported

InfoTrack 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

maps to

Microsoft Dynamics 365 Sales

Activity (Appointment / Task)

1:1
Fully supported

InfoTrack 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

maps to

Microsoft Dynamics 365 Sales

Invoice

1:1
Fully supported

InfoTrack 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

maps to

Microsoft Dynamics 365 Sales

No Equivalent — Custom Reference Field

1:1
Fully supported

InfoTrack'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

maps to

Microsoft Dynamics 365 Sales

User

1:1
Fully supported

InfoTrack 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

maps to

Microsoft Dynamics 365 Sales

Custom Fields on Matter Entity

1:1
Fully supported

InfoTrack 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.

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.

InfoTrack logo

InfoTrack gotchas

High

InfoTrack is a workflow layer with no standalone CRM data model

Medium

Custom folder sync for documents requires Time Matters 16.6+

High

No public API means bulk export requires manual CSV downloads

Medium

Integration keys must be regenerated when reconnecting to a new case management system

Medium

Per-order invoice granularity complicates matter-level billing reconstruction

Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales gotchas

High

Professional tier 15-table custom table limit blocks migrations

High

October 2024 pricing increase applies at renewal for all customers

Medium

Custom fields must be created in the UI before API writes

Medium

Power Platform request limits apply to bulk migrations

Medium

Activity records orphaned to inactive owners fail silently

Pair-specific challenges

  • InfoTrack has no native CRM objects — matter-to-opportunity mapping requires a custom Dataverse table

    Unlike HubSpot or Salesforce migrations where objects map 1:1, InfoTrack stores legal-matter records that have no direct Dynamics 365 Sales equivalent. We create a custom Matter entity in Dataverse to serve as the primary record, then link it to Accounts and Contacts. Dynamics 365 Sales Professional's 15-table limit may be constraining for high-complexity legal setups — Enterprise or Premium unlocks unlimited custom tables. We surface this during discovery so the Dynamics license tier is confirmed before migration runs.

  • InfoTrack's eFiling and process-serving workflows cannot migrate and must be rebuilt in Power Automate

    InfoTrack's core value — automated eFiling submission, process-server dispatch, and docket-return syncing — lives in platform-specific workflows that have no export mechanism. These are not data records; they are configured automation logic. Dynamics 365 Sales has no native eFiling or court-docket-sync capability. We export InfoTrack workflow definitions as a reference document (triggers, conditions, actions) so your team can rebuild equivalent flows in Power Automate. The legal-automation rebuild is a separate project engagement outside the data-migration scope.

  • InfoTrack practice-management integration links break and require a separate re-integration plan

    InfoTrack integrates with Time Matters, LEAP, and Clio via bidirectional sync links that push matter data, document references, and order status back to the practice-management system. Dynamics 365 Sales is not a practice-management platform — there is no native bridge to Time Matters or LEAP. We preserve the integration endpoint URLs in a custom reference field on each Matter record, but rebuilding the bidirectional sync requires a separate integration project using Dynamics 365's Web API or a third-party middleware tool such as KingswaySoft or Scribe.

  • InfoTrack pay-per-use pricing history may not represent a true revenue figure for pipeline reporting

    InfoTrack invoices reflect per-transaction billing — a single matter may generate dozens of eFiling, search, and process-serving charges over its lifetime. These transactions do not map to a single Dynamics 365 Sales revenue figure for the opportunity. We map service orders to Order records, but the aggregate matter value for pipeline forecasting needs a business-rule decision from your team: sum all historical charges, use estimated total matter value, or use only active-order amounts. We surface this as a pre-migration configuration decision.

  • SharePoint document storage must be provisioned before document migration runs

    InfoTrack documents are retrieved from InfoTrack's storage and uploaded to Dynamics 365 Sales' connected SharePoint environment. If SharePoint document libraries are not provisioned and connected to your Dynamics 365 Sales instance before migration, document migration will fail or route to the wrong library. We require confirmation of SharePoint setup (library names, folder structure by matter) before the document migration phase begins. Dynamics 365 Sales Professional includes SharePoint integration; verify your license includes document management before migration.

Migration approach

Six steps for a successful InfoTrack to Microsoft Dynamics 365 Sales data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

InfoTrack logo

InfoTrack

Source

Strengths

  • Covers US federal, bankruptcy, and state court eFiling in a single platform with real-time docket syncing.
  • Bidirectional sync with integrated case management systems means court-returned documents and expenses land directly in the Matter without manual steps.
  • Pay-per-use model with no subscription, no per-seat licensing, and no setup fees for firms with variable litigation volume.
  • Integrated process serving network with up to five attempts per order and automated status updates.
  • Pre-population of court forms from Matter data reduces data entry errors and accelerates filing turnaround.

Weaknesses

  • InfoTrack is not a standalone practice management system—it requires an integrated case management system to manage contacts, matters, and client billing.
  • No documented public API for bulk data retrieval; all exports require manual CSV download from the admin panel.
  • Limited to US federal and state court workflows; not applicable for international, immigration, or transactional law practices.
  • Credit card processing fees and state-variable ACH fees add cost complexity for high-volume litigation firms.
  • Integration key loss during onboarding requires a support ticket to resolve, creating friction when reconfiguring integrations.
Microsoft Dynamics 365 Sales  logo

Microsoft Dynamics 365 Sales

Destination

Strengths

  • Native integration with Microsoft 365, Teams, Outlook, and SharePoint for unified productivity workflow
  • Unlimited custom tables and complex workflows on Enterprise tier enable deep customization for complex sales processes
  • AI-driven predictive analytics and deal intelligence on Enterprise and Premium tiers help sales teams prioritize pipeline
  • Dataverse unified data layer provides a consistent API and data model across all Dynamics 365 and Power Platform apps
  • Strong security model with Field-Level Security and Record Ownership rules for governance-conscious enterprises

Weaknesses

  • Sales Professional tier caps custom tables at 15, creating a migration ceiling for highly customized SMB environments
  • October 2024 pricing increases of $15 per user across all tiers apply to existing customers upon renewal
  • Implementation typically requires costly certified partners, adding 30–50% to total project cost
  • Updates and platform releases can disrupt customizations and plugins, requiring regression testing after each wave
  • Non-Microsoft integrations require additional configuration or middleware, limiting flexibility for heterogeneous tech stacks

Complexity grading

How hard is this migration?

Standard CRM migration. 1 of 8 objects need a manual workaround.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across InfoTrack and Microsoft Dynamics 365 Sales .

  • Object compatibility

    B

    1 of 8 objects need a manual workaround.

  • 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

    InfoTrack: Not publicly documented.

  • Data volume sensitivity

    B

    InfoTrack doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your InfoTrack to Microsoft Dynamics 365 Sales 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 InfoTrack to Microsoft Dynamics 365 Sales data migrations

Answers to the questions buyers ask most during InfoTrack to Microsoft Dynamics 365 Sales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most InfoTrack-to-Dynamics 365 Sales migrations complete in 3–6 weeks for setups with under 10,000 matter records. Complex migrations with 50,000+ records, custom entity development, and multi-party matter structures extend to 2–4 months. The longest phase is discovery and schema planning — mapping InfoTrack's legal-domain records to CRM objects requires business-rule decisions that affect every downstream mapping. Additional time may be needed for SharePoint document migration and Power Automate workflow design.

Adjacent paths

Related migrations to explore

Ready when you are

Move from InfoTrack.
Land in Microsoft Dynamics 365 Sales , 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