Migrate from Tofu to HighLevel

Tofu Accounts represent target companies in the ABM model. We export Account name, industry, tier classification, owner email, and any custom enrichment fields. GoHighLevel's Company object receives the Account data directly. We use Company name as the dedupe key to prevent duplicate records. If GoHighLevel's account limit applies on the Starter plan, we confirm account count during scoping.

Tofu Campaigns are the top-level container for landing pages, email sequences, ads, and collateral tied to a targeting strategy. We export all campaign metadata including status, start and end dates, targeting criteria, and linked Account associations. In GoHighLevel, Campaigns receive the campaign metadata as standard Campaign fields (Name, StartDate, EndDate, Status). The targeting logic from Tofu (linked Accounts and Audience memberships) is preserved as a GoHighLevel Campaign Member list built from the exported Account IDs.

Tofu Playbooks encode multi-step outreach sequences with conditional branching based on prospect engagement signals. GoHighLevel Workflows model automation as linear step sequences with triggers, conditions, and actions. We decompose each Tofu Playbook into discrete Step records during export, then reconstruct the steps as GoHighLevel Workflow actions in sequence order. Any conditional branching that cannot be represented linearly is preserved as custom text fields on each Workflow step (e.g., original_condition__c) for the GoHighLevel admin to reconfigure in the Workflow builder. The workflow inventory handoff document lists every original Playbook, its steps, and the recommended GoHighLevel trigger and action equivalents.

Tofu Personas define the ICP profile — industry, role, pain points, and messaging tone — used to personalize content. We export persona definitions as structured records with their field values. GoHighLevel does not have a native Persona object. We create a custom field group on the Contact record (persona_industry__c, persona_role__c, persona_pain_points__c, persona_messaging_tone__c) and map each Tofu Persona field to its equivalent custom field. Audience associations that link Personas to Accounts are preserved as GoHighLevel Contact Tags.

Tofu Audiences are filtered subsets of Accounts or Contacts used to trigger Playbook activation. We export audience membership as a list of linked Account IDs along with the filter criteria. GoHighLevel has no native Audience object, so we create a Tag for each Audience name (e.g., Enterprise Tier A, Mid-Market A) and apply it to all Contact records that were members of that Audience in Tofu. The original filter criteria are documented in a custom field on the Tag record for future reference.

Tofu Content Assets include landing pages, one-pagers, ads, and sales collateral with metadata, version history, and linked Campaign/Account associations. Binary assets live on Tofu's CDN. We export asset metadata and re-download binaries from Tofu's asset URLs at export time. In GoHighLevel, we create Document records carrying the asset metadata (name, type, version, linked Campaign). The original CDN URL is stored in a custom field asset_source_url__c so that any inaccessible assets are flagged during pre-flight validation before the final sync.

Tofu Users are assigned as Campaign owners and Playbook creators. We export user email addresses, names, and role assignments. GoHighLevel User records are matched by email address. Any Tofu Owner without a matching GoHighLevel User is held in a reconciliation queue pending User provisioning by the GoHighLevel admin. Owner assignments on Accounts, Campaigns, and Playbook steps are resolved against the User mapping before record import begins.

Tofu supports custom fields on Accounts, Campaigns, and Playbooks. We detect all non-standard properties during the pre-migration schema scan, document their data types, and recreate them as equivalent GoHighLevel custom fields before any data import. Picklist-type custom properties become GoHighLevel dropdown fields; text fields map to text inputs; numeric fields map to number fields. The full custom field inventory is included in the migration scope document.