Migrate from LeadSimple to Microsoft Dynamics 365 Sales

LeadSimple Leads map directly to Dynamics 365 Leads. The Lead Name, email, phone, address, source, and referrer fields map to corresponding Lead entity attributes. Stage Name maps to the Lead Status field; original stage-enter timestamps are preserved in custom datetime fields on the Lead record for historical continuity.

LeadSimple leads that have progressed past a defined qualification threshold (e.g., stage = 'Lease Signed') split into Dynamics 365 Contacts. Contacts are created with a link to the corresponding Account (Property) record. This split logic is configurable per your LeadSimple stage configuration — we surface the split criteria before the migration runs.

LeadSimple Properties map directly to Dynamics 365 Accounts — the property name becomes Account Name, address fields map to Address1 composite fields, Property Type maps to a custom Industry-type pick-list, and Annual Contract Value (ACV) maps to a custom Number field (Annual_Contract_Value__c). Occupancy status migrates as a custom Occupancy_Status__c pick-list field.

LeadSimple Units require a custom entity in Dynamics 365 since Dataverse has no native child-of-account rental-unit entity. We create a new_Unit table with lookup to Account, and fields for Unit_Number, Number_of_Units, Rent_Amount, Occupancy, and Lease_End_Date. If your LeadSimple Units contain custom fields, those become additional custom fields on new_Unit.

LeadSimple Processes own all workflow automation, auto-triggers, and conditional stage-change logic. These records do not migrate — the logic must be rebuilt in Power Automate or Dynamics 365 Business Process Flows. We export Process definitions as a reference document (JSON export of trigger/action rules) to give your Dynamics admin a rebuild blueprint.

LeadSimple tasks (Next Task Kind, Next Task Due At) map to Dynamics 365 Task records. Subject, Due Date, Priority, and Status map directly. Owner is resolved by email match against Dynamics 365 SystemUser records. Unmatched owners are flagged for admin resolution before final migration.

LeadSimple comments on Leads and Processes migrate to Dynamics 365 Annotation records (Notes). Each comment becomes a separate Note record linked to the corresponding Lead or Account entity. Comment author and timestamp are preserved in the Note's CreatedBy and CreatedOn fields. Since LeadSimple's bulk export does not include comments, we retrieve them via API in a secondary pass.

LeadSimple tag lists are many-to-many — a Lead can have multiple tags, and a tag applies to multiple Leads. Dynamics 365 has no native tag/label entity, so we create a custom new_Tag table and a Lead_Tag junction table (new_lead_tag) to preserve the full tag structure. Each tag value becomes a new_Tag record; junction records link Lead to Tag.

LeadSimple contact custom fields (which differ per owner/tenant per property) map to Dynamics 365 Contact custom fields. Note that Dynamics 365 does not support per-relationship custom field variation — all contacts receive the same set of custom fields. If a LeadSimple contact-level field was conditionally visible, we flag it for admin review post-migration.

LeadSimple Pipelines map to Dynamics 365 Opportunities with a one-pipeline-per-Opportunity mapping. Stage Name in LeadSimple maps to Opportunity StageName via value-by-value mapping. For multi-pipeline LeadSimple setups, each pipeline maps to a separate Opportunity record type or a custom Pipeline_Name__c field to maintain segregation.

LeadSimple's Annual Contract Value (ACV) is a numeric property-level field. When a LeadSimple Lead is associated with a Property, the ACV migrates as Opportunity Estimated Revenue. If the Lead has no Property association, ACV is stored as a custom custom_ACV__c field on the Opportunity for reference.

Dynamics 365 sets CreatedOn at the time of record creation in the destination. To preserve the original LeadSimple create date for reporting continuity, we store it as a custom Original_Create_Date__c datetime field on the Lead entity. This is essential for teams that track time-in-stage based on the original entry date.