Migrate from Altcraft to HighLevel

Discovery and export method selection

We audit the source Altcraft installation across tier (Cloud, Cloud Pro, Private Cloud, or On-premise), Profile count, active Campaigns, Segments (static and dynamic), Automation Scenarios, custom field definitions, Control Group assignments, and e-commerce data (Products and Orders). We also identify the export path: UI-based CSV export for Cloud tiers, Albato connector credentials for customers with active middleware, or direct database credentials for Private Cloud and On-premise installations where the customer provides them. The discovery output is a written migration scope with an export method recommendation and a preliminary field mapping draft.

GoHighLevel workspace and custom field preparation

We create the destination structure in GoHighLevel before any data import: Contact Custom Fields matching every Altcraft custom field type (string, date, number, checkbox, dropdown), Tags for channel subscriptions and Control Group membership, Contact Lists for static segment migration, and Campaigns with historical performance metrics. We disable validation rules on custom fields during import to prevent rejection from format mismatches, and re-enable them after the delta-validation pass.

Profile export and data quality remediation

We export Altcraft Profiles via the identified export method (CSV, Albato, or database). During export, we apply data quality transformations: email lowercasing, phone number formatting, date standardization, and custom field type normalization. Any records with missing required fields (email or name) are flagged in a remediation queue for the customer's Altcraft admin to resolve before import proceeds. We generate an export manifest with record counts by segment, campaign, and lifecycle stage.

Lead-Contact split and Control Group preservation

We apply the Lead-Contact split rule defined during scoping: early-stage profiles route to GoHighLevel Lead, qualified profiles route to GoHighLevel Contact. We preserve the original Altcraft lifecycle stage in a custom field on each record. We also embed the Altcraft Profile ID and any Control Group membership as explicit attributes in the export CSV so that after GoHighLevel assigns its own IDs, we can re-attach Control Group assignments using the reconciliation key.

GoHighLevel import in dependency order

We import records into GoHighLevel in dependency order: Contact Lists (static segments) first, then Contacts and Leads (with the split applied), then Campaigns (with performance metrics), then Products, then Opportunities (for e-commerce orders). Each phase emits a row-count reconciliation report before the next phase begins. We import through GoHighLevel's REST API with rate-limit handling and exponential backoff. After contacts land with GoHighLevel IDs, we run the Control Group reattachment step by matching on the altcraft_profile_id__c reconciliation key and applying the appropriate tags.

Delta migration and Scenario inventory delivery

We run a final delta migration of any records modified in Altcraft during the migration window (new sign-ups, profile updates, campaign sends). We deliver the Automation Scenario inventory document describing each active Scenario's trigger, conditions, actions, and recommended GoHighLevel Workflow equivalent. We do not rebuild Scenarios as GoHighLevel Workflows inside the migration scope. We conduct a reconciliation walkthrough with the customer's GoHighLevel admin, confirming record counts, tag assignments, Control Group membership, and campaign data integrity before cutover is confirmed.