Migrate from Wired Plus to Salesforce Sales Cloud

Wired Plus contacts migrate to Salesforce Lead if the contact is pre-qualified (no active deal association and lifecycle status indicating a marketing-qualified stage), and to Salesforce Contact if the contact has an associated deal or represents a confirmed customer. We query the Wired Plus lifecycle_stage or equivalent status field during extraction and apply the split rule at migration time. The original Wired Plus consent flags (opt_in, source) are preserved in a custom field wp_original_consent__c on both Lead and Contact for GDPR documentation.

Wired Plus company records map directly to Salesforce Account. The company domain or website field becomes the Account's Website field and serves as the dedupe key during import. Account is created before any Contact import so that the AccountId Lookup is satisfied at the moment of Contact insert.

Wired Plus Deals map to Salesforce Opportunity. The Wired Plus deal stage maps to Salesforce StageName using a stage-mapping table we build during scoping, where each source stage name is matched to a destination stage in the Salesforce Sales Process. Closed-Lost and Closed-Won deal states map to the corresponding Salesforce stage entries. Amount, expected close date, and deal owner transfer directly.

Wired Plus pipeline stages are defined per account. We extract the full stage sequence, probability values, and ordering during scoping and configure a Salesforce Sales Process that mirrors the source pipeline. Each stage maps to a Salesforce StageName value. Stages with no equivalent in Salesforce are flagged in the mapping document and the customer's admin chooses the closest replacement during sign-off.

Wired Plus campaigns (email send history, open rates, click data) migrate to Salesforce Campaign records. Campaign name, status, type, and start/end dates transfer directly. Open rate, click rate, and send volume migrate as custom fields on the Salesforce Campaign record since Salesforce Campaign Member statistics are computed from CampaignMember records rather than stored as fields. Automated workflow triggers export as metadata only.

Wired Plus tags (flat string labels on contacts and companies) migrate to Salesforce multi-select picklist fields on Contact and Account. The customer chooses the tag strategy during scoping: direct multi-select picklist migration or Salesforce Topics with TopicAssignment for broader cross-object use. Tag name uniqueness is enforced at migration time to prevent picklist value overflow.

Wired Plus account-specific custom fields on contacts require API-based schema resolution before export. We fetch the field schema via the Wired Plus API during scoping to map field labels to internal field IDs, then create matching Salesforce custom fields (with __c suffix) before migration. Field types (text, date, number, picklist) map to equivalent Salesforce field types. Picklist values migrate as Salesforce picklist options. Labels that changed between the export and the scoping audit are flagged for manual correction.

Custom fields on Wired Plus deals migrate to Salesforce custom fields on Opportunity. We follow the same API-based schema resolution process as for contacts. Deal-level custom field types that have no Salesforce equivalent (for example, multi-select formats that exceed picklist limits) are flagged in the mapping document with a recommended configuration approach.

Wired Plus landing pages export as HTML content and asset URLs. We deliver the exported HTML and asset archive to the customer. Salesforce Sales Cloud has no native landing page builder; the customer's marketing team rebuilds pages in their chosen platform (Experience Cloud, Marketo, or a third-party landing page tool). We flag any pages with embedded forms that require a new form handler ID.

Wired Plus forms capture subscriber data and link to campaigns or landing pages. We export field names, form configurations, and submission logs. Form-to-field mappings must be rebuilt at the destination since form handler IDs are platform-specific. We deliver a form field inventory document to guide the rebuild in Salesforce Web-to-Lead or Experience Cloud.

Wired Plus automation workflows define trigger-action sequences including conditional branches and time delays. We export workflow definitions as structured metadata (JSON where the API supports it, or a manual walkthrough of the workflow builder). The trigger events, delay values, condition logic, and downstream actions are documented in a written inventory for the customer's admin to reconfigure in Salesforce Flow. We do not migrate workflows as executable code.

File attachments stored within Wired Plus records are not reliably accessible via the standard export interface. We recommend exporting attachments separately via direct download before migration begins. The customer can reattach files to Salesforce records post-migration or store them in Salesforce Files (ContentDocument) with a manual relinking step.