Migrate from Wired Plus to Microsoft Dynamics 365 Sales

Wired Plus Contacts map to Dynamics 365 Contact records. We create an Account record for each unique company domain in Wired Plus before Contact import so that AccountId is resolved at insert time. The contact's Wired Plus pipeline stage maps to a custom field wp_original_pipeline_stage__c on the Contact since Dynamics 365 tracks pipeline progression in the Opportunity object, not on Contact. Opt-in consent flags (opt_in, source fields) map to Dynamics email preference fields (EMailOptOut, DoNotEmail) to preserve consent status for GDPR compliance.

Wired Plus Company records map to Dynamics 365 Account. Company domain maps to Account.Website, Company name maps to Account.Name, and any industry or employee count fields map to typed Account custom fields. We deduplicate on Company_ID or domain where present. Account is created before Contact to satisfy the required parent relationship.

Wired Plus Deals map to Dynamics 365 Opportunity. Each Wired Plus deal links to a Contact or Company; we resolve the parent AccountId and ContactId at migration time and set the Opportunity's AccountId. Deal amount maps to Opportunity.Amount, close date maps to Opportunity.CloseDate, and the Wired Plus pipeline stage maps to a custom Opportunity field wp_original_stage__c with the Dynamics 365 stage set via the configured Sales Process.

Each Wired Plus pipeline stage value maps to a Dynamics 365 Opportunity Stage in a Sales Process that we configure before migration. Stage probability percentages transfer from Wired Plus to StageProbability on the corresponding stage. If Wired Plus has multiple pipelines, we create multiple Record Types on Opportunity, each with its own Sales Process scoped to the relevant stage values.

Wired Plus campaigns migrate to Dynamics 365 Campaign records with campaign name, status, and start/end dates preserved. Campaign performance metrics (open rate, click rate, send volume) transfer to Campaign custom fields since Dynamics 365 Campaign tracks response metrics rather than engagement rates directly. The campaign email templates themselves are exported as content and flagged for rebuild in Dynamics 365 Marketing or a third-party email platform.

Wired Plus automation workflows define trigger-action sequences with conditional branches and delays. We export workflow definitions as structured JSON metadata. The trigger event IDs, condition logic, and time delays require complete manual reconfiguration in Power Automate or Dynamics workflow because Wired Plus workflow syntax is not transferable. We provide a workflow audit log listing every active workflow with trigger type, conditions, and recommended Power Automate template as the rebuild reference.

Wired Plus landing pages export as HTML content and asset URLs. We deliver the HTML, form field definitions, and submission logs as structured files. The forms themselves must be rebuilt at the destination; form handler IDs are Wired Plus-specific and not portable. We recommend Power Pages, SharePoint with Power Automate, or a third-party form platform as the rebuild target.

Wired Plus form field definitions export with field names, types, and submission logs. The form-to-contact field mappings are not transferable because Wired Plus form handler IDs are platform-specific. We deliver a form inventory document listing every form, its field schema, and the target platform recommendation. Form submissions (historical data) migrate as Contact records with a source attribution field.

Wired Plus account-specific custom fields on Contact, Company, and Deal require field-level mapping to Dynamics 365 custom fields. We extract the field schema via the Wired Plus API during scoping (field label, type, picklist values), then provision matching custom fields in Dynamics 365 with correct field types (text, number, date, picklist, boolean). Field labels that have changed since last export require manual correction before mapping.

Wired Plus tags are flat string labels on Contact and Company. We export all tag assignments and reapply them as a Dynamics 365 custom multi-select picklist on the Contact object. If the tag count exceeds Dynamics 365 picklist limits, we use a text field with comma-separated values. The customer chooses tag strategy during scoping.