Migrate from Corteza CRM to Microsoft Dynamics 365 Sales

Corteza Lead records map directly to Microsoft Microsoft Dynamics 365 Sales Lead. Standard fields (firstname, lastname, email, phone, company, rating) migrate to the corresponding Dataverse Lead attributes. We resolve the lead status and source campaign reference at migration time. Lead scores and custom qualification fields migrate as custom fields on the Lead entity.

Corteza Account records map to Dynamics 365 Account. The account name becomes Account.Name, industry classification maps to IndustryCode, and address data maps to Address1 fields with Address2 handling any secondary address. Account is created before any Contact import so that the parentcustomerid_account lookup is satisfied at Contact insert time.

Corteza Contact records map to Dynamics 365 Contact. The parent Account relationship migrates by resolving the Corteza Account GUID to the Dynamics 365 Account record ID via a lookup table built during the Account migration phase. Job title, email, phone, and address fields map directly. Custom fields on the Corteza Contact module migrate as custom attributes on the Dataverse Contact entity.

Corteza Opportunity records map to Dynamics 365 Opportunity. The deal stage maps to StageName, amount maps to EstimatedValue, probability maps to closeprobability, and closedate maps to EstimatedCloseDate. The parent Account lookup resolves via the Account mapping table. Custom opportunity fields migrate as custom Opportunity attributes.

Corteza Campaign records map to Dynamics 365 Campaign. Campaign type, status, budget, and target metrics migrate as Campaign attributes. CampaignMember records linking Contacts and Leads to the Campaign migrate as Dynamics 365 CampaignActivity and CampaignMember records. Actual costs and response tracking data migrate to CampaignResponse if available in the Corteza source data.

Corteza Case records map to Dynamics 365 Case (Incident) if the destination tenant includes Customer Service. Case status, priority, origin, and resolution fields map to the corresponding Case attributes. The parent Account and Contact lookups resolve via the Account and Contact mapping tables created during earlier migration phases. Case number migrates to CustomerNumber for reference integrity.

Corteza Task records map to Dynamics 365 Task. Status, Priority, ScheduledEnd (due date), and Description migrate directly. Task assignment migrates by resolving the Corteza owner reference to the Dynamics 365 User via email match. The Regarding (regardingobjectid) lookup resolves to the parent Lead, Account, Contact, or Opportunity record using the ID mapping tables built during those phases.

Corteza call engagement records map to Dynamics 365 Task with TaskSubtype set to Call. Call duration, disposition, and recording URL (if stored in Corteza) migrate to custom Task fields. The activity timestamp preserves the original engagement date so the sales timeline reflects the correct sequence of events.

Corteza meeting engagement records map to Dynamics 365 Appointment (the Dynamics 365 term for calendar Event records). Start time, end time, location, and organizer migrate as Appointment attributes. Attendee references resolve to Contact or Lead records via the Contact mapping table and link via the AppointmentParty (attendees) multi-select field.

Corteza email engagement records map to Dynamics 365 Email (emailactivity) records. The email body, subject, sender, and recipients migrate as Email attributes with the From (emailsender) and To (emailrecipients) resolved to Contact or Lead records via the mapping tables. Email timestamps preserve the original sent date for timeline accuracy.

Corteza custom modules — created via the low-code builder with non-standard field types and custom validation rules — migrate to Dataverse custom tables. We pre-create the destination schema (table name, columns, data types, relationships) in the Dynamics 365 maker portal before any data import. Lookup fields within custom modules resolve via mapping tables built for standard Corteza entities. Customers choosing Microsoft Dynamics 365 Sales Hub attach custom tables to the Common Data Model used by Power Apps and Power Automate.

Corteza Product records map to Dynamics 365 Product. Product name, SKU, description, and pricing information migrate as Product attributes. If the Corteza instance uses price lists, these map to the Dynamics 365 PriceList entity with PriceLevelItem records for pricing entries. Product status (active/inactive) maps to StateCode.