Migrate from Wise Agent to HighLevel

Wise Agent contacts map directly to HighLevel contacts. Every standard field (name, email, phone, address) passes through unchanged. Custom properties on the contact record create HighLevel Custom Fields during migration — type-matched (text, number, pick-list) and applied to the contact record in HighLevel.

Wise Agent's company/record object maps to HighLevel's Company object. The company name, website, address, industry, and employee-count fields pass through directly. Annual revenue stored as text in Wise Agent is transformed to a numeric amount field in HighLevel Companies. Additional metadata such as company type, tax ID, or custom properties are preserved as HighLevel Custom Fields, ensuring a complete profile after migration.

Wise Agent transactions map to HighLevel Opportunities. The deal name, amount, stage, and close date translate directly. However, Wise Agent stores property address, buyer/seller role, and checklist progress on the transaction record — these become HighLevel Custom Fields on the Opportunity. The stage label in Wise Agent maps to the nearest HighLevel pipeline stage pick-list value.

Wise Agent notes migrate to HighLevel Notes with the original body text, create date, and owner preserved. Rich-text formatting in Wise Agent notes is preserved as HTML in HighLevel's note body field. Notes are linked to the parent contact or company record by email-address matching against the HighLevel contact.

Wise Agent calendar entries and scheduled appointments migrate to HighLevel Appointments with the original start/end datetime, title, assigned user, and location field preserved. The appointment owner is resolved by email match against HighLevel users before the record lands. Recurring appointments generate separate HighLevel appointment records, and any custom properties such as meeting type or client notes are mapped to HighLevel Custom Fields on the Appointment object.

Wise Agent tasks and reminders map directly to HighLevel Tasks with the task title, due date, status, and priority preserved. Owner assignment follows the email-match resolution process used throughout the migration. Incomplete tasks in Wise Agent land as Open tasks in HighLevel.

Wise Agent labels applied to contacts map to HighLevel Tags on the Contact record. Each unique label in Wise Agent becomes a Tag value in HighLevel. If a contact has multiple labels in Wise Agent, all corresponding tags are applied to the HighLevel contact record.

Wise Agent drip campaign enrollments with enrollment dates and step progress do not map to a live HighLevel object. We export enrollment data as a JSON rebuild-reference file so your HighLevel admin can configure corresponding Workflow triggers. The enrollment timestamp is preserved as a custom field (Drip_Enrolled_Date__c) on the Contact for re-enrollment logic.

Wise Agent SMS history is stored as text activity on the contact record. HighLevel does not replicate Wise Agent's inbound/outbound SMS thread — we import the message content as a HighLevel Note tagged with the message timestamp, direction (sent/received), and SMS type label for reference. HighLevel Conversations must be reconnected to your SMS provider on the destination side.

Wise Agent transaction templates with checklist steps and role assignments have no native equivalent in HighLevel. We export the template structure as a JSON rebuild-reference document including step names, role assignments, and default due-date offsets. Your HighLevel admin recreates these as pipeline task templates or workflow-generated task sequences.

Wise Agent custom properties per contact become HighLevel Custom Fields on the Contact object. Each custom property's data type (text, number, date, pick-list) is identified during the data audit and the corresponding field type is created in HighLevel before migration. Pick-list custom properties require value-by-value mapping against HighLevel's pick-list options.

Wise Agent custom properties on company/record objects migrate to HighLevel Custom Fields on the Company object using the same type-matching logic as contact custom properties. Company-level custom fields are created before the migration run so all values land in the correct fields.

Wise Agent team members and agent owners are resolved by email match against HighLevel users. Unmatched owners are flagged before the migration so your team can invite them to HighLevel first or assign records to a fallback owner. Role-based permissions (admin, agent, assistant) do not migrate — HighLevel permission sets are configured on the destination side.

Wise Agent marketing programs (email campaigns, broadcast lists) map to HighLevel Campaigns with the program name, create date, and status preserved. Campaign membership and send history are not replicated — the campaign record is created as a reference object and your HighLevel admin links contacts using the exported campaign membership data.