Migrate from Act-On to HighLevel

Act-On Contact records migrate directly to GoHighLevel Contact. Standard fields (name, email, phone, company) map cleanly. Act-On lifecycle stage, source tracking, and engagement score migrate to custom Contact fields we create during schema setup. GoHighLevel does not have a native lifecycle stage field; we create a custom field act_lifecycle_stage__c to preserve the original value for segmentation reference.

Act-On Companies map to GoHighLevel Account. Company name, industry, and address fields map to Account name, industry classification, and billing address. The one-to-many Contact-to-Company relationship resolves during import: each Contact record carries the parent Company identifier and we attach it to the Account via GoHighLevel's Contact-to-Account link.

Act-On Lists are audience segments used for campaign targeting. We preserve List membership as GoHighLevel Tags on the Contact record. Static Lists (manually maintained) produce definitive tags. Dynamic Lists (rule-based) we flag as requiring Smart List recreation in GoHighLevel because the rule definition does not export. We provide a List-to-Tag mapping table as part of the migration inventory.

Act-On Programs are multi-step nurture sequences with defined entry criteria, branches, and delays. The Program definitions do not export via API. We extract which Contacts entered which Programs and when, and we write Program names and entry dates into custom Contact fields (e.g., program_name__c, program_entry_date__c). This historical record informs the GoHighLevel Workflow rebuild, which the customer's admin executes using that data as a reference blueprint.

Act-On email send history, subject lines, and engagement events (opens, clicks) migrate as entries in GoHighLevel's Contact activity timeline. We write timestamped activity records for each email event with the subject and engagement type preserved. HTML content does not transfer as a reusable template in GoHighLevel; we document template names and content as a separate asset inventory for the customer's team to rebuild.

Act-On form field definitions and submission data migrate. We write submission records as GoHighLevel Contact entries with form field data mapped to custom Contact fields named for the original form field. The form embed code does not transfer; GoHighLevel Forms replace Act-On web forms, and we document the mapping from each Act-On form to its GoHighLevel equivalent.

Act-On's Custom Data schemas define user-extended fields on Contact or Company. We read the schema definition via Act-On's Custom Objects API, export existing records, and write them to GoHighLevel. If the Act-On custom field is contact-level (one value per contact), we create an equivalent GoHighLevel Contact custom field. If the Act-On custom object represents a related entity (e.g., a property linked to a contact), we create a GoHighLevel Custom Object with a relationship to Contact.

Act-On calculates engagement scores using proprietary weighting across email opens, clicks, page visits, and form submissions. These formulas do not export. We migrate the current numeric score as a static Contact custom field (act_engagement_score__c). Score recalculation must be configured manually in GoHighLevel using GoHighLevel's own scoring rules or a third-party scoring integration.

Email opens, clicks, form submissions, and other behavioral events export as timestamped activity log entries on the GoHighLevel Contact record. Activity types map to GoHighLevel activity categories. Large activity volumes (over 200,000 records) we chunk by date range to manage API throughput and avoid timeout failures.

Act-On Contact and Company tags export as label arrays. We map them directly to GoHighLevel Tags on the Contact record. Tags used for classification (e.g., industry, intent level) migrate verbatim; the customer decides whether to use tags as GoHighLevel Smart List membership criteria or as purely descriptive labels.