Migrate from Convert Wire to Microsoft Dynamics 365 Sales

ConvertWire Contact maps directly to Dynamics 365 Sales Contact. The primary company association on ConvertWire creates an AccountId lookup — if the contact has no linked company, FlitStack attaches it to a default 'Unassigned Account' record to satisfy Dynamics 365 Sales' required AccountId on contacts.

ConvertWire Contacts with status values indicating unconverted prospects (Lead, Marketing Qualified, Sales Accepted) route to Dynamics 365 Sales Lead records. Contacts marked as Customer, Active, or Closed Won route to Contact records directly. The split logic applies the ConvertWire lifecycle-status mapping table generated during discovery.

ConvertWire Company maps to Dynamics 365 Sales Account. Company hierarchies (parent-subsidiary) translate to the Parent Account ID field in Dynamics 365 Sales. Multi-company associations that ConvertWire allows N:N become a primary Account link plus Account Contact Relationships in Dynamics 365 Sales.

ConvertWire Deal maps to Dynamics 365 Sales Opportunity. The Deal's linked Contact and Company create the Opportunity's CustomerId (Account) and optionally generate OpportunityContactRoles for the associated contacts. Deal stage maps to Opportunity StageName via the pipeline-specific value mapping table. If a Deal references multiple contacts, each contact receives its own OpportunityContactRole entry to preserve relationship history.

Each ConvertWire pipeline becomes a Dynamics 365 Sales Business Process Flow linked to a Sales Process. In Dynamics 365 Sales Professional, pipelines share a single sales process. In Enterprise, each ConvertWire pipeline can become a separate Sales Process with its own stage definitions and process flow.

Stage names map value-by-value per pipeline. ConvertWire stage-entered timestamps preserve as custom datetime fields on Opportunity since Dynamics 365 Sales overwrites stage-change timestamps on standard fields. Probability weights and forecast category re-applied from Dynamics 365 Sales stage configuration. These custom fields ensure historical stage entry dates are available for reporting and audit purposes.

ConvertWire email engagement records become Dynamics 365 Sales Email (activity) records. The Regarding field links to the parent Contact or Opportunity. Email body, subject, direction (inbound/outbound), and timestamp preserve from ConvertWire. Attachments re-upload to Dynamics 365 Sales SharePoint integration. Any embedded images within the email body are preserved as attachments and stored alongside the email record.

ConvertWire call logs map to Dynamics 365 Sales PhoneCall activity records. Subject, call duration, direction, phone number, and outcome notes carry over. The Regarding link connects the call to the source Contact or Opportunity in Dynamics 365 Sales. If the call includes a disposition code, it is stored in a custom field on the PhoneCall record.

ConvertWire meeting records map to Dynamics 365 Sales Appointment activities with original start/end times, location, and body preserved. Required/optional attendees resolve to Dynamics 365 Sales Contact or User records by email match. The Regarding link attaches the meeting to the relevant Opportunity or Account.

ConvertWire notes migrate as Dynamics 365 Sales Annotations (Notes). Title, body text, created date, and owner preserve. The objectid and objecttypecode fields on the annotation link the note to the parent Contact, Account, or Opportunity in Dynamics 365 Sales. If a note contains an @mention to a user, the mention is recorded as a NoteRegarding reference to that user record.

ConvertWire custom properties stored on Contact, Company, or Deal objects become custom columns on the corresponding Dataverse table in Dynamics 365 Sales. FlitStack creates the custom columns during schema setup and maps data types (text, number, picklist, date) to matching Dataverse column types.

ConvertWire owner IDs resolve to Dynamics 365 Sales SystemUser records by email address match. Unmatched owners are flagged in the migration report — your admin either invites them to Dynamics 365 Sales before migration or assigns their records to a fallback owner to avoid null OwnerId errors on Opportunities.