Migrate from REDA to Microsoft Dynamics 365 Sales

REDA stores contacts in Salesforce's Contact object. Dynamics 365 uses the Contact table on Dataverse. Standard fields (name, email, phone, title) map directly. The Contact's AccountId lookup resolves REDA's Company association — if no matching Account exists, records land under a placeholder until Accounts migrate.

REDA contacts without a primary company association or with a 'prospect' designation route to the Dynamics 365 Lead table. Leads are persons not yet tied to an Account. The Lead's CompanyName and Address fields map from REDA's contact-level address properties.

REDA's Company object is Salesforce Account with custom fields for property count, lease status, and developer type. Maps to Dynamics 365 Account with Account Name, Website, Industry, and address fields. REDA's parent-company hierarchy uses Salesforce ParentId — preserved as the Parent Account lookup in Dynamics 365.

REDA's Deal object maps to Dynamics 365 Opportunity. Deal name, amount, close date, and owner transfer directly. Pipeline stage in REDA is a Salesforce Sales Process stage — maps to Dynamics 365 Opportunity Stage pick-list, with value-by-value mapping per process if multiple pipelines exist.

REDA's Property object is a Salesforce custom object (Property__c) tracking building name, address, unit count, and property type. In Dynamics 365 Sales Enterprise, we create a Dataverse custom table named 'Property' with equivalent columns. Relationship to Account uses the Account ID lookup.

REDA Lease records (Lease__c) track tenant, property, lease start/end dates, monthly rent, and deposit amounts. Migrate as a Dataverse custom table named 'Lease' with a lookup to the Property table and a lookup to the Contact (tenant) record. Lease status (Active/Terminated/Draft) maps as a Status field.

REDA Unit records (Unit__c) are children of Property, tracking unit number, floor, square footage, and occupancy status. Each Unit links to its parent Property via a lookup. In Dynamics 365, create a Unit custom table with a lookup to Property and fields for unit identifier, size, and current lease status.

REDA task records—including logged calls and follow‑up items—migrate as Dynamics 365 Task rows, transferring Subject, Description, Due Date, Priority, and Status fields directly. The Regarding (regardingobjectid) lookup associates each task with its parent Account, Contact, or custom Property/Lease record, while the OwnerId resolves via email matching to the corresponding Dynamics 365 SystemUser. Status codes are mapped value‑by‑value to preserve workflow continuity.

REDA's EmailMessage records migrate as Dynamics 365 Email activity records. Subject, Body (plain text or HTML), From, To, and sent date transfer. Attachments are re-hosted as Dynamics 365 attachments on the email record. The regarding lookup attaches the email to the CRM record.

REDA calendar events are migrated as Dynamics 365 Appointment rows, bringing over Subject, Start Time, End Time, Location, and Required Attendees. The Regarding (regardingobjectid) lookup attaches the appointment to the related Account, Contact, or Opportunity, while the REDA owner’s email is matched to the Dynamics 365 SystemUser to set the correct Organizer. Optional description and recurrence patterns are preserved where applicable.

REDA file attachments on Property, Lease, or Contact records are re‑uploaded to Dynamics 365 as Note rows, storing the binary content as a documentbody column or linking to a SharePoint document location for larger files. The Regarding (regardingobjectid) lookup ties each note to its parent record, while original file names, MIME types, and creation timestamps are retained to maintain audit continuity and traceability.

REDA records carry an OwnerId pointing to a Salesforce User. FlitStack resolves each Salesforce User's email against Dynamics 365 user principal names. Unmatched owners are flagged with a custom 'Source Owner ID' field and assigned to a designated fallback Dynamics 365 user until the team maps them manually.