Migrate from Constructor to Microsoft Dynamics 365 Sales

Constructor account records map directly to Dynamics 365 Account. The Account Name maps to the Account.Name field; Constructor's company address fields map to the composite address fields in Dynamics 365's address schema (street, city, state, postalcode, country). Additional standard fields such as phone, website, industry code, and employee count are also transferred to the corresponding Account attributes, preserving all core business data.

Constructor contact properties map to Dynamics 365 Contact fields. The primary key is ContactId in Dynamics. If Constructor stores multiple companies per contact, we map the primary company to AccountId (lookup) and surface additional companies as Account Contact Roles in Dynamics 365.

Constructor leads with status='new' or 'contacted' route to Dynamics 365 Lead. Leads already converted in Constructor (status='qualified') route to both Contact and Account, with the Lead record retained as a reference. We split by Constructor's lead status code value_mapping. Unqualified leads are imported as inactive Leads, preserving historical data for reporting. Lead source, rating, and custom scoring fields map to the corresponding Dynamics 365 Lead attributes.

Constructor opportunities map to Dynamics 365 Opportunities. Each Opportunity requires an AccountId (or Account lookup). Constructor's pipeline stage maps to Dynamics 365 process stage via Business Process Flow assignment per opportunity. Close date and estimated revenue map directly. Probability values and forecast category assignments transfer to the corresponding Dynamics 365 fields, and opportunity attributes are preserved as Dataverse columns. Owner resolution follows same email‑match process used for accounts and contacts.

Constructor's pipeline object maps to a Dynamics 365 Business Process Flow. Each Constructor pipeline creates its own BPF in Dynamics 365 so stage names, probabilities, and progression logic are scoped per pipeline. BPF activation requires Dynamics admin configuration after schema setup.

Constructor call logs migrate as Dynamics 365 PhoneCall activities or Tasks with Type='Phone'. Original timestamps, call duration, owner, and parent record (Contact or Opportunity) links are preserved. Direction (inbound/outbound) maps to DirectionCode in Dynamics. Call notes are transferred to the PhoneCall description field. If the call is linked to a Contact, the regarding field points to the Contact record; if linked to an Opportunity, the regarding field references the Opportunity.

Constructor email records map to Dynamics 365 Email activities. Subject, body (plain text or HTML), sender, recipients, and timestamps migrate. Attachments are downloaded and re-uploaded to Dynamics 365 SharePoint or Notes attachments per destination's file storage configuration. Email status (sent, received, draft) is stored in the Email.Status field, and flags map to the Email.Priority attribute. If the source email references a Contact or Opportunity, the regarding field is set accordingly.

Constructor meeting records map to Dynamics 365 Appointments. Start time, end time, location, organizer, and attendee list are preserved. If Constructor stores meeting notes separately, they migrate as Note records linked to the Appointment. The appointment subject and description are taken from the Constructor meeting title and details. The organizer field maps to the Dynamics 365 user who created the meeting.

Constructor notes migrate as Dynamics 365 Annotations. The note subject, body text, created date, and owner are mapped. If the note references a specific record in Constructor, we preserve the object reference as a custom field (SourceObjectId__c) for traceability. Any file attachments on the note are transferred to the related Annotation's file attachments, and note language or HTML formatting is retained in the body.

Constructor products map to Dynamics 365 Product records. Product name, SKU, unit price, and product type (service vs. inventory) migrate. If Constructor stores product bundles, we map those as Dynamics 365 Product Bundles with bundled items. Product description, unit, and hierarchy categories are transferred to the corresponding Dynamics 365 Product fields. Pricing details are linked through Price List Items, and stock tracking flags are set according to the inventory type.

Any Constructor custom field that has no direct Dynamics 365 equivalent is created as a custom column in the Dataverse table. We preserve the data type (string, integer, decimal, picklist, boolean, datetime) and option-set values as a Global Option Set in Dynamics 365 when applicable.

Constructor owner IDs are resolved by email address against Dynamics 365 SystemUser records. If a Constructor owner has no matching Dynamics user, we flag the record before migration—your admin either creates the Dynamics user or assigns those records to a fallback owner designated for migration.