Migrate from FilePro to Microsoft Dynamics 365 Sales

FilePro Client records map directly to Dynamics 365 Account. The client name maps to Account.Name, address fields map to Address1_City, Address1_State, Address1_PostalCode, and the primary contact email maps to EmailAddress1 on the primary Contact. Multi-practice clients (those with matters across practice areas) are mapped as a single Account with each Matter represented as a separate Opportunity record.

Each FilePro Matter becomes a Dynamics 365 Sales Opportunity linked to the Account created from the parent Client. Matter name maps to Opportunity.Name; Matter number is preserved in a custom Opportunity column (Matter_Number__c). The Matter status (Active, Closed, Archived) maps to Opportunity StateCode — Open = 0, Won = 1, Lost = 2. Practice area (Family, Criminal, Corporate) maps via value_mapping to a custom Opportunity column (Practice_Area__c).

Contacts stored on a FilePro Matter (client contacts, referring attorneys, opposing counsel) map to Dynamics 365 Contact records. Each Contact is linked to the parent Account via AccountId lookup. The Contact's role on the Matter (Client, Referrer, Opposing Counsel) is preserved as a custom Contact column (Matter_Role__c) and as an Opportunity Contact Role in Dynamics 365.

FilePro time entries are high-volume and carry Date, Duration, Description, Billable flag, and hourly rate. Dynamics 365 standard Activities (Task, PhoneCall) do not carry a billable-rate field. FlitStack creates a custom Dataverse table (Time_Entry__c) with columns Date__c, Duration_Minutes__c, Description__c, Billable__c, and Rate__c, linking each entry to the parent Opportunity via OpportunityId. If the firm uses Dynamics 365 Business Central for billing, the custom table can sync via a Power Automate flow.

FilePro documents and attachments are re-uploaded as Dynamics 365 Notes (Annotation entity). The document filename maps to Annotation.Filename, the content maps to DocumentBody (base-64 encoded), and MIME type maps to MimeType. Files are linked to their parent record (Account, Opportunity, or Contact) via ObjectId. SharePoint document management can be enabled in Dynamics 365 as an alternative storage target — files are re-uploaded to the SharePoint library and the annotation record points to the SharePoint URL.

FilePro UDFs on the Client table become custom columns on the Dynamics 365 Account table. Each UDF requires a new column definition in Dataverse (e.g., Client_Source__c for a Referral Source picklist, Client_Referral_Balance__c for a currency field). Picklist UDFs in FilePro require OptionSet value-mapping in Dynamics 365 — FlitStack generates the mapping table during the schema build phase.

FilePro UDFs on the Matter table map to custom columns on the Dynamics 365 Opportunity table. For trust accounting UDFs (Trust Balance, Unbilled Disbursements), FlitStack creates a separate custom Dataverse table (Trust_Accounting__c) linked to the Opportunity so the fields do not clutter the standard Opportunity form layout. The custom table approach mirrors FilePro's flat-field model while keeping Dynamics 365 clean for sales users.

FilePro billing records (invoices generated from time entries) can map to Dynamics 365 Quotes and Orders if the firm uses Dynamics 365 Sales for client invoicing. Each FilePro invoice line maps to a QuoteProduct or OrderProduct row. If the firm uses a separate practice management or accounting system for billing, FlitStack maps invoice records to a custom Dataverse table (Legacy_Invoice__c) for reference — these records are not synced to the Dynamics 365 Quote/Order entities unless Dynamics 365 Business Central is in scope.

FilePro operator logins are matched to Microsoft 365 users by email address. FlitStack checks each FilePro user against the Azure AD tenant connected to Dynamics 365 — matched users receive OwnerId assignment on their migrated records. Unmatched operators (e.g., former staff) are flagged and assigned to a placeholder SystemUser (e.g., 'FlitStack Migration' user) so record ownership is valid in Dynamics 365.

FilePro calendar entries map to Dynamics 365 Appointments (ActivityPointer entity). Subject maps to Subject, Start Time maps to ScheduledStart, End Time maps to ScheduledEnd, and Description maps to Description. Location and attendees are mapped from FilePro appointment fields if present. Each Appointment is linked to the relevant Account or Opportunity via regardingobjectid.

FilePro notes and memos attached to a Matter are migrated as Dynamics 365 Notes (Annotation) linked to the corresponding Opportunity record. The note text maps to Annotation.Notetext, and the FilePro note date maps to CreatedOn for audit continuity. If notes contain embedded file references, the linked files are exported separately and re-attached as described in the Document mapping.

FilePro trust account records (receipts, disbursements, running balance) have no direct equivalent in standard Dynamics 365 Sales. FlitStack creates a custom Dataverse table (Trust_Accounting__c) with columns Trust_Type__c, Amount__c, Transaction_Date__c, Description__c, and Reference__c, linked to the parent Opportunity. This preserves the trust accounting history for compliance purposes even if the firm migrates billing to Dynamics 365 Business Central post-migration.