Migrate from Wired Plus to Pipedrive

Wired Plus Contact records map to Pipedrive Person objects, which combine individual and organization data into a single record. The Wired Plus email field maps directly to Pipedrive's email field, and opt_in status is preserved in the Wired_Plus_opt_in custom field to document consent provenance. We flag contacts where the opt_in field is absent or false to prevent unintended marketing re-engagement at the destination.

Wired Plus Company records map to Pipedrive Organization. We use Company_Name and domain fields as dedupe keys. Organization is created before any Person import so that the Person-Organization link is satisfied at insert time. If a Wired Plus contact has no linked company, we create a stub Organization record using the contact's domain.

Wired Plus Deals map to Pipedrive Deals with stage, value, and owner preserved. The Wired Plus deal stage maps to a Pipedrive Pipeline stage. Deal value (numeric) migrates to Pipedrive's numeric value field. We resolve the Person and Organization lookups at migration time using email and company name matching.

Wired Plus pipeline stages defined per account extract as a named stage sequence. We create a Pipedrive Pipeline with stages named to match the Wired Plus stage labels, preserving order. Stages with no equivalent in Pipedrive are flagged and marked as archived stages in the handoff documentation.

Wired Plus Campaign records contain send history, open rates, click rates, and status. Pipedrive has no native Campaign object. We extract campaign metrics and attach them as read-only custom fields on the Person record (for example, last_campaign_name, last_email_opened_date, total_email_opens). This preserves the reporting history without requiring a separate object.

Wired Plus custom fields are account-specific with field labels that differ from internal IDs. We pull the field schema via the Wired Plus API during scoping, resolve each label to its internal identifier, then map to Pipedrive custom fields of the matching type (text, number, date, dropdown). Field types that Pipedrive does not support (for example, multi-checkbox from Wired Plus) map to multi-select picklists or text fields depending on content.

Wired Plus tags are flat string labels on contacts and companies. We export all tag assignments and reapply them as a custom field (Tag) on the Pipedrive Person or Organization record. If the customer prefers, tags can be stored as comma-separated values in a single text field to preserve the full tag set without creating Pipedrive labels that require ongoing maintenance.

Wired Plus automation workflows define trigger-action sequences with conditional branches and time delays. We export workflow definitions as structured JSON metadata but do not migrate them to Pipedrive automations because the trigger event IDs, delay values, and condition logic require complete manual reconfiguration. We deliver a written workflow audit log that lists each workflow name, trigger type, conditions, and actions for the customer admin to rebuild in Pipedrive's Automation rules.

Wired Plus landing pages are stored with HTML content and form configurations. We export page HTML and asset URLs as a file package. Any pages with forms that submit to a Wired Plus form handler are flagged because the form handler IDs do not exist in Pipedrive and the forms must be rebuilt at the destination. We provide a page inventory listing each landing page URL, form fields, and submission handler status.

Wired Plus Forms capture subscriber data linked to campaigns or landing pages. We export form field names and submission logs as structured data. The form-to-field mappings do not transfer because Pipedrive does not have a native form builder at the CRM layer (it uses LeadBooster Web Forms or marketplace form tools). We deliver a form field inventory for the admin to rebuild using their chosen form tool.

File attachments stored within Wired Plus records are not reliably accessible via the standard export interface. We flag this during scoping and recommend that the customer exports attachments via direct download before migration day. Attachments do not transfer through the migration API; the customer handles them separately and re-links them post-migration if needed.