Migrate your InfoTrack data

InfoTrack does not own the Matter object—it references Matters from the integrated case management system. When migrating into InfoTrack, the Matter must exist in the connected system (Clio, LEAP, Time Matters, etc.) first. When migrating out, we pull Matter data from the case management system and map InfoTrack orders and expenses to the corresponding Matter records.

Orders are the core transactional record in InfoTrack, capturing service type (eFiling, process serving, SignIT), court, party details, status, and cost. We export Orders as structured CSV or through the admin panel. In migration, each Order is mapped to a new Matter at the destination and its associated Expenses and Documents are linked to the same target Matter.

InfoTrack invoices export as CSV from the admin Billing > Invoices tab with invoice number, date, line items, amount, and payment status. We map these to the destination's billing module or import them as financial records. Note that per-order pricing means each filing generates its own invoice line item rather than a consolidated monthly statement.

Litigation service expenses are recorded in the integrated case management system as orders are placed. We export the expense ledger as part of the invoice CSV and map each expense to its corresponding Matter at the destination. The expense-to-Matter linkage is preserved so that billing reconciliation against client matters is intact after migration.

Court-filed and court-stamped documents sync back to the Matter in the case management system. We flag any documents stored within InfoTrack's own repository and download them manually before account closure, as InfoTrack has no public bulk-download API. Documents must be associated with the correct Matter at the destination, which requires mapping InfoTrack order IDs to destination Matter IDs.

InfoTrack does not store a contact database. Party names on filings are pulled from the integrated case management system. We handle contact migration separately through the connected system (Clio, LEAP, etc.), which holds the canonical contact record.

User management is split between InfoTrack (admin credentials, integration keys, billing users) and the case management system (attorneys, paralegals, assignees). We export InfoTrack user roles and integration credentials from the admin panel. User assignment to Matters must be re-established at the destination since InfoTrack does not own the user-Matter relationship.

Firms typically connect InfoTrack to one primary case management system via an integration key or OAuth flow. We export the list of active integrations and their configuration details. Re-establishing the integration at the destination requires generating a new integration key from InfoTrack's admin panel and entering it in the new case management system.

InfoTrack maintains a vetted network of process servers. Order metadata includes server assignment, attempt counts, and status. We export this metadata as part of the Order record and map it to the equivalent service tracking field at the destination.

CSV invoice exports from the Billing > Invoices tab include the full billing history. We ingest this into the destination's billing module or hold it as a financial reconciliation record. Note that InfoTrack invoice records are expense-level, not matter-level, so we cross-reference with the Expenses export to produce a matter-level billing summary at the destination.

Custom field capability is determined by the integrated case management system rather than InfoTrack. Any custom fields used for litigation-specific data must be migrated from the case management system. We map these at the system level and preserve custom field values against the corresponding Matter at the destination.