Migrate from ActiveDEMAND to HighLevel

ActiveDEMAND Contacts with standard fields (name, email, phone, company) map directly to GoHighLevel Contact. Custom Brand Custom Fields export first as a schema, then as data values loaded into GoHighLevel Location custom fields. The Contact.email field serves as the dedupe key during import. Multi-community operators should designate a community assignment field during scoping — either a GoHighLevel Tag or a custom Contact field — before loading begins.

ActiveDEMAND Companies map to GoHighLevel Company records. The Company.name field becomes the Company name in GoHighLevel, and Company.address fields map to the billing address on the GoHighLevel Company. Where ActiveDEMAND contacts have no Company assigned, GoHighLevel creates a placeholder Company record to satisfy the relationship. Duplicate Company names merge based on exact name match during the load phase.

ActiveDEMAND Campaigns (email, funnel, multi-channel) carry membership data that maps to two GoHighLevel objects: campaign membership becomes a Tag on the Contact record (e.g., Tag = 'Campaign: Q1 Lead Nurture'), and campaign-level deal or pipeline data (if present in ActiveDEMAND) becomes a GoHighLevel Opportunity with the campaign name as the Opportunity name. The campaign type distinction (email vs funnel vs event) is preserved in a custom field campaign_type__c on the Contact Tag.

ActiveDEMAND call records include source number, destination number, call duration, recording URL, and linked Contact. We load these as GoHighLevel Tasks with TaskSubtype = Call, preserving the duration in a custom numeric field and the recording URL in a custom text field. The original ActiveDEMAND call disposition maps to a custom picklist field on the Task. The Contact lookup resolves via email match against the imported Contact records.

ActiveDEMAND website chat conversations (timestamps, message text, visitor contact info) export as structured data and load as GoHighLevel Notes linked to the Contact. The Note title carries the conversation date range; the Note body carries the full message transcript. Visitor-sourced contacts without an existing GoHighLevel Contact are created first, then the Note is linked.

ActiveDEMAND Appointment records (date, time, status, linked Contact, community reference) map to GoHighLevel Calendar Events linked to the Contact by email resolution. The appointment status (confirmed, cancelled, no-show) maps to a custom picklist field on the Event. Community references from ActiveDEMAND carry as Tags on the Contact record.

ActiveDEMAND Forms and their field definitions export as metadata. We deliver a written field mapping for each form showing ActiveDEMAND field names and their GoHighLevel form field equivalents. Form bodies (HTML/CSS) are preserved as attachment references for manual reassembly in GoHighLevel's form builder. This is a manual rebuild step; we do not import ActiveDEMAND forms as live GoHighLevel forms.

ActiveDEMAND Landing Pages and Funnel Builder stages export as structured metadata including page URLs, funnel stage names, and contact-stage assignments. We deliver a stage mapping table showing how ActiveDEMAND funnel stages map to GoHighLevel pipeline stages. Full funnel reassembly in GoHighLevel's funnel builder is a manual step for the customer's admin team.

ActiveDEMAND Brand Custom Field schemas vary per account and must be exported before Contact records so that the equivalent GoHighLevel custom fields are created first. We export the schema definition, identify the GoHighLevel field type match (text, number, date, picklist, checkbox), create the fields in GoHighLevel at the Location level, then load the data. Skipping schema-first causes custom field data to land in default fields or drop silently.

ActiveDEMAND Contact Lists and Segments export as a static list of Contact IDs per list. Each list becomes a GoHighLevel Tag assigned to every Contact ID in that list. GoHighLevel's tag model is flat (no nested segments), so any multi-level segment hierarchy in ActiveDEMAND flattens to a single Tag level — we document the hierarchy in the handoff notes.

ActiveDEMAND Automated Workflows are exported as structured metadata (workflow name, trigger conditions, step count, action types). We do not migrate workflows as code. We deliver a written workflow inventory listing each ActiveDEMAND workflow with its trigger, conditions, and recommended GoHighLevel Workflow equivalent. The customer's admin rebuilds workflows in GoHighLevel's visual workflow builder.

File attachments to ActiveDEMAND contacts, campaigns, or forms export by URL reference. We download files to local storage and re-upload to GoHighLevel, maintaining filename and MIME type. The file is linked to the corresponding Contact or Company record by ID resolution after the parent record has been created in GoHighLevel.