Migrate from Wired Plus to HighLevel

Wired Plus Contact records map directly to GoHighLevel Contact records. The core fields (email, first_name, last_name, phone) migrate without transformation. We query opt_in, consent_source, and subscription_status fields explicitly during extraction because these flags are not always included in default Wired Plus CSV exports; failing to do so creates GDPR risk at the destination. We set HasOptedOutOfEmail and EmailOptedIn appropriately on the GoHighLevel Contact to preserve the original consent state.

Wired Plus Company records exist as a related object to Contacts and may contain domain, address, and industry fields. GoHighLevel uses Contact records with a company_name field rather than a separate Company object in the standard schema. We extract Company_Name, domain, and any custom company-level fields and merge them as custom properties on the parent Contact record. Where a Company_ID field exists, we use it as the dedupe key to avoid duplicate company entries during contact import.

Wired Plus Deals map to GoHighLevel Opportunities. The deal_name maps to Opportunity name, deal_value maps to Opportunity value, and the Wired Plus pipeline stage maps to a GoHighLevel Pipeline stage. We extract the full stage sequence during scoping and create the equivalent GoHighLevel Pipeline before migration so that stage values are valid at import time. Custom deal fields resolve to GoHighLevel custom Opportunity fields by label matching against the account schema.

Each Wired Plus account defines its own pipeline stages, which are not standardized across accounts. We extract the complete stage sequence during discovery, then create matching GoHighLevel Pipeline stages with the same names and approximate probabilities. Any stages with no direct equivalent are flagged for the customer's admin to review and assign. This step is required before Deal import because GoHighLevel rejects Opportunities with invalid stage names.

Wired Plus campaigns with send history and performance metrics migrate to GoHighLevel Campaigns. We export campaign name, status, send date, open rate, click rate, and bounce data. GoHighLevel Campaign records are available but campaign-level automation triggers (Wired Plus trigger-action sequences attached to campaign sends) do not transfer. We store campaign performance metrics as custom properties on the Contact record so that reps can see which campaign sourced each contact without a native campaign analytics view.

Wired Plus tags are flat string labels applied to contacts. We export all tag assignments per contact and import them as GoHighLevel Tags. GoHighLevel supports tagging at the contact level and allows tag-based filtering in workflows and campaigns. Tags that contain special characters or exceed GoHighLevel's length limits are sanitized before import and logged for admin review.

Wired Plus custom fields use field labels rather than internal field IDs in CSV exports, and labels can change between exports. We resolve field labels to internal identifiers via the Wired Plus API during scoping, then map each to a corresponding GoHighLevel custom field created before import. Picklist values and field types (text, number, date, checkbox) are matched to GoHighLevel field types. Any Wired Plus custom field with no GoHighLevel equivalent is flagged for schema extension.

Wired Plus automation workflows define trigger-action sequences including conditional branches and time delays. GoHighLevel's Workflow engine uses a different trigger-action model with different condition syntax, delay expressions, and action types. We export workflow definitions as structured JSON metadata and deliver a written Workflow Audit documenting each active workflow's trigger, conditions, actions, and recommended GoHighLevel Workflow equivalent. The customer's admin rebuilds these in GoHighLevel's visual workflow builder; we do not convert the automation logic as code.