Migrate from Actito to HighLevel

Actito Profiles are the central record type and map directly to GoHighLevel Contacts. Standard profile attributes (email, first name, last name, phone) map to GoHighLevel's default Contact fields. Custom profile attributes migrate as GoHighLevel custom fields on the Contact record. We inspect the full attribute list during scoping, create matching custom fields in GoHighLevel before migration, and import Profiles with all attributes intact.

Actito Custom Tables are user-defined schemas linked to Profiles via relationships. We inspect each table's field types and cardinality. Tables with one-to-one attribute semantics become GoHighLevel custom fields on the parent Contact. Tables with one-to-many or independent record semantics (e.g., property records, subscription history rows) are restructured as separate GoHighLevel Contacts with a tag-based or custom field link back to the parent Contact, or as JSON-serialised data in a long-text custom field if the volume is high.

Actito Entities partition all resources within a licence. GoHighLevel Sub-accounts provide equivalent isolation for agencies managing multiple clients. During scoping we determine whether the Actito entities represent separate client environments (map to GoHighLevel Sub-accounts) or internal business units (map to GoHighLevel tags and pipeline filters). Sub-account creation happens in GoHighLevel before the migration begins.

Actito campaigns span email, SMS, push, call center, print, and web channels. We migrate campaign configuration metadata (name, schedule, targeting criteria, channel assignments) as structured configuration records. Individual channel content (email body, SMS text) migrates as GoHighLevel custom field values or template references. Channel-specific DNS authentication (DKIM, SPF) is flagged for re-setup on GoHighLevel's LC Email infrastructure.

Actito Scenarios are event-triggered automation workflows with branching logic and multi-channel actions. These do not migrate as executable code because GoHighLevel Workflows use a different trigger-action model. We map every active Scenario and deliver a written inventory document with trigger type, conditions, branching rules, and action steps annotated with the equivalent GoHighLevel Workflow construction. The customer's admin or a GoHighLevel specialist rebuilds the workflows post-migration.

Each Actito channel has its own sender, template, and routing configuration. We migrate channel setup metadata (sender name, sender email, routing rules) and flag DNS authentication records that must be reconfigured on GoHighLevel's LC Email (Mailgun-based) and LC Phone (Twilio-based) infrastructure. Dedicated sending domains and warm-up procedures are documented as a post-migration checklist item.

Profile-level opt-in, consent flags, double opt-in status, and channel-level preferences migrate as structured custom fields on the GoHighLevel Contact. GDPR compliance attributes (right to be forgotten, data processing basis) preserve in dedicated custom fields. Multi-language preference migrates to a language custom field. The full preference tree is audited during scoping to ensure all consent records land in the correct GoHighLevel custom field.

Actito's Export API definitions (file naming patterns, scheduling, compression type) are documented as job specifications. GoHighLevel does not have a direct export-definition equivalent. We map the export job intent to a GoHighLevel Workflow with an API action step that calls the Actito export endpoint (if Actito remains running in parallel) or document the job as a customer IT task for rebuilding with GoHighLevel's native integrations.

Actito web tracking goals and behavioural event definitions migrate as configuration records. We map goal names, trigger conditions, and associated profile attributes to GoHighLevel custom fields and workflow triggers. GoHighLevel's native tracking pixel is documented for re-deployment post-migration as the new event source.

Interaction events (opens, clicks, bounces, unsubscribes) are generated by Actito's platform during campaign execution and are not available for programmatic export. We do not migrate engagement history. We advise exporting and archiving all available Actito campaign reports before cutover. GoHighLevel campaign reporting starts from the go-live date forward.