Migrate from Lemon Tech to Microsoft Dynamics 365 Sales

Lemon Tech standard Entities (the primary data container covering organizations, firms, or case-related parties) map to Dynamics 365 Account. We use Entity export to pull all standard entity records and map the primary identifier to Account.Name. For legal-specific entity types that represent firms or clients rather than individual persons, Account provides the organizational container. Standard entity fields migrate as typed Account fields; any fields without a direct Account equivalent become custom fields on Account.

Lemon Tech Contact records map directly to Dynamics 365 Contact with all standard fields (name, email, phone, address) preserved. Custom contact properties identified during discovery migrate as custom fields on Contact. The email address serves as the dedupe key during import. Account is resolved from the parent Entity mapping before Contact import so that the parent account lookup is satisfied at insert time.

Lemon Tech Matters (the primary legal case or project container with date, status, and billing linkage) map to Dynamics 365 Opportunity because both track a named business entity with stage progression, associated contacts, and financial amounts. Matter status, Matter open/close date, and any billable amount fields map to Opportunity StageName, CloseDate, and Amount. The original Matter identifier is preserved in a custom field lemon_matter_id__c for audit traceability.

Lemon Tech Matter status values (such as Open, Pending, Closed, Billed) map to Dynamics 365 Opportunity StageName values that we configure in the destination org during schema setup. Stage probabilities are assigned per stage. If the customer uses custom Matter statuses, we create custom Opportunity Stage values rather than forcing them into standard Dynamics 365 stages.

Lemon Tech User records map to Dynamics 365 User by email address match. Name and role information migrate to the User record. Owner assignments on Matters, Contacts, and custom Entities resolve via this User mapping. Any Lemon Tech User without a matching Dynamics 365 User goes to a reconciliation queue for the customer's admin to provision before record import proceeds.

Custom Entities created in Lemon Tech via API or UI export via the Entity-level export function. We inventory all active custom entity types during discovery, then pre-create the equivalent Dataverse custom table in Dynamics 365 including all custom fields, data types, and lookup relationships. Custom entity naming conventions (which vary by firm due to no enforced standard) are normalized to a consistent API naming format during mapping. Original names are preserved in a metadata field.

SQL Wrappers that export structured relational data (simple wrappers without multi-table joins or computed columns) map to Dataverse custom tables we pre-create during schema setup. We export the wrapper as a structured table and map field names to Dataverse column definitions. Complex wrappers with nested SQL logic, external data sources, or computed columns are flagged during discovery and treated as requiring manual re-implementation rather than automated migration because the computed result may not be reproducible without the original SQL definition.

File attachments associated with Lemon Tech Entities, Matters, or Contacts export as binary blobs via the export function. We preserve the original filename, file type, and association to the parent record type and ID. In Dynamics 365, attachments map to Annotation records (for notes and small files) or to SharePoint document locations if the customer's implementation uses Dynamics 365's native SharePoint integration for file management.

Time entries and billing records linked to Matters export via the Entity export. Billable hours, rates, and amounts map to custom fields on the related Opportunity (as line-item-style custom fields) or to a custom billing table depending on the customer's Dynamics 365 configuration. If the customer licenses Dynamics 365 Project Service or Finance, we scope billing record mapping separately during discovery.