Migrate from Agillic to HighLevel

Schema enumeration and discovery

We extract the complete Agillic recipient schema using the Recipient API (GET /recipients with all properties returned) and cross-reference with a Recipients Export snapshot. We enumerate every active custom recipient property, its data type, and its usage frequency. We also extract Global Data Table schemas, Flow names and trigger events, and confirm whether the Flow Execution ID setting is enabled under Settings > System Settings > Export > Activity Exports. We audit the complete Activity history date range and volume per channel.

GoHighLevel schema design

We design the GoHighLevel destination schema based on the Agillic enumeration. Standard recipient fields (email, name, phone, language, opt-in flags) map to GoHighLevel Contact standard fields. Custom recipient properties become GoHighLevel Custom Fields of matching type. Each Agillic Global Data Table becomes a GoHighLevel Custom Object with Unique Fields configured per the Agillic primary key logic and reference fields for foreign key relationships. We create this schema in a GoHighLevel sandbox first for validation.

Sandbox migration and reconciliation

We run a full migration into GoHighLevel sandbox using production-like data volume. The customer reconciles record counts (Contacts imported, Custom Object records imported, Activity Notes created), spot-checks 25-50 random Contacts against the Agillic source for field accuracy and custom property completeness, and verifies that Activity timelines reconstruct correctly on Contact records. Any mapping corrections happen here, not in production.

Production migration in dependency order

We run production migration in record-dependency order. Contacts import first using email as the dedupe key. Custom Objects import second, with Unique Fields preventing duplicates. Global Data Table rows import third, resolving reference fields to Custom Object records. Activity history (email send/open/click, SMS, events) imports last as Notes and Tasks on the Contact record, preserving timestamps. Each phase emits a row-count reconciliation report before the next phase begins.

Flow Execution ID preservation and template handoff

We preserve Agillic Flow Execution IDs as custom text fields on the relevant Contact records. We deliver a written inventory of every Agillic Flow (name, trigger, associated channels, and execution frequency) mapped to a recommended GoHighLevel Workflow equivalent. We deliver Template content and field mapping documentation for manual rebuild in GoHighLevel's email builder. We do not rebuild Flows, Templates, or automation logic in GoHighLevel as part of the migration scope.

Cutover, validation, and post-migration support

We freeze Agillic writes during cutover, run a final delta migration of any records modified during the migration window, then enable GoHighLevel as the system of record. We deliver a reconciliation report comparing Agillic record counts against GoHighLevel import counts. We support a one-week hypercare window to resolve data issues raised by the customer's team. We do not provide post-migration admin training, GoHighLevel Workflow rebuild, or ongoing support as standard scope.