Migrate from RunSensible to Microsoft Dynamics 365 Sales

RunSensible clients migrate as Dynamics 365 Accounts. Client name maps to Account.Name. The client's primary contact name optionally populates the Account's primary contact field. Billing address, shipping address, and communication preferences on the client record become the Account's corresponding address and preference fields in Dynamics 365.

RunSensible contacts migrate as Dynamics 365 Contacts. The contact's associated client record determines the AccountId lookup in Dynamics 365. Each contact must resolve to a parent Account before migration, so Accounts are migrated first in the sequence. Email addresses and phone numbers map to the standard contact communication fields.

RunSensible Matters are the central legal entity and map to Dynamics 365 Opportunities. Matter name becomes Opportunity.Name. Matter status (Open, Closed Won, Closed Lost) maps to the Opportunity State and Status fields. Practice-area classification and other legal metadata become custom columns on the Opportunity.

RunSensible practice-area pick-list values such as Personal Injury, Corporate, Family Law, or Real Estate have no direct Dynamics 365 equivalent. A custom pick-list field Practice_Area__c is created on the Opportunity table and populated from the source matter type value-by-value, preserving the full legal taxonomy from RunSensible.

RunSensible tracks a statute-of-limitations date per matter. A custom datetime field Sol_Date__c is created on Opportunity and populated from RunSensible. This field is not native to Dynamics 365 Sales and must be maintained as a custom column or shown in a sub-grid on the opportunity form.

RunSensible records the court and jurisdiction for each matter — including trial court, appellate court, federal or state level, and geographic jurisdiction codes. A custom text field Court_Jurisdiction__c is created on the Opportunity record. Pick-list values are mapped one-by-one from the RunSensible jurisdiction list to the Dynamics 365 custom field options.

RunSensible time entries (date, duration, description, billable flag) migrate as Dynamics 365 Tasks. The task Subject is built from the matter name and entry description. Billable hours and rate information is stored in a custom field on the Task since Dynamics 365 Activities do not natively track billing rates.

RunSensible tasks attached to a matter migrate as Dynamics 365 Tasks with the same subject line, due date, priority, and status flags. Owner resolution uses email address matching against Dynamics 365 user records. Unresolved owners are flagged in a pre-migration report and must be assigned a fallback owner before the migration commits.

RunSensible logged emails and calls linked to a matter migrate as Dynamics 365 Email and PhoneCall activity records. The original timestamp, direction (inbound/outbound), and subject line are preserved. The activity is attached to the Opportunity record via the regardingobjectid lookup.

RunSensible documents attached to a matter migrate as Notes or Attachments in Dynamics 365. Files are re-uploaded to the Opportunity's related documents section. Salesforce-like SharePoint integration is not native to Dynamics 365 Sales Professional — documents attach directly to the record by default.

RunSensible's invoicing and billing records have no native Dynamics 365 Sales equivalent — the CRM does not include a billing module. Invoices are exported as a structured CSV and can be stored as a custom entity or referenced via a related SharePoint document library. Trust-account data is exported separately for compliance reference.

RunSensible's built-in conflict-checking flag — conducted against the client database before matter intake to identify potential conflicts of interest — has no native Dynamics 365 equivalent. The conflict-check result (cleared, cleared with waiver, or conflict) is stored as a custom text field Conflict_Check__c on the Account record for reference and bar-compliance documentation.

RunSensible custom fields on any entity map to custom columns in Dynamics 365. Field types are matched (text to text, date to datetime, pick-list to pick-list). RunSensible Professional tier limits apply to custom field counts — Enterprise or Premium tier in Dynamics 365 is recommended for firms with more than 15 custom fields.