Migrate your FilePro data

Clients are the primary party records in FilePro's legal data model. We extract them as delimited ASCII from their spin-off file and map them directly to Contacts or Account objects in the destination CRM. Client addresses, phone numbers, and email fields are migrated as standard properties.

Matters are the case-level records tied to a Client. We preserve the full Matter record including Matter number, description, open/close dates, responsible lawyer assignment, and Matter type. Matter-stage values are mapped to the destination's pipeline stages or a custom field where no native pipeline exists.

FilePro allows each firm to define custom fields per record type. These UDFs are exported as additional columns in the spin-off file. We flag every UDF during scoping and discuss whether each maps to a native destination field, a custom field, or requires a transformation pass before loading.

Time and activity records are stored in a separate spin-off file linked to Matters and Users. We export the full time ledger including date, duration, billing rate, description, and billable/non-billable flag. Where the destination uses a different time-entry object model, we merge time records into the closest equivalent.

FilePro manages document storage paths and links. We export the file path registry and, where feasible, the document metadata (filename, type, created date, associated Matter). We do not migrate the binary file bodies themselves — we map the path registry so the firm can re-link documents after migration.

FilePro maintains trust account balances and transaction history for client funds. These are exported as ledger entries linked to the Client record. We map the running balance and transaction type (receipt, disbursement, transfer) but recommend a separate reconciliation step post-migration given the sensitivity of trust data.

FilePro does not have a native visual pipeline board. Firms that track Matter status in a workflow field export it as a text or coded value. We map these status values to the destination pipeline stages, preserving the ordering logic the firm has used.

Contact records are distinct from Client records in FilePro. We treat them as standard Contact objects in the destination CRM, preserving name, role, email, phone, and the relationship to the parent Client.

FilePro generates invoices and records payments against Matters. We export the invoice header and line items, payment date, and amount applied. Because FilePro uses a firm-specific billing structure, we review the invoice template during scoping and map line items to the destination's equivalent billing object.

User records in FilePro include name, role, and permission level. We export the full user roster and map each to the destination's Owner/User assignment. Active versus inactive status is preserved as a lifecycle flag.