Migrate from Devi to HighLevel

Customer-provided export and discovery

We request that the customer provide a full data export from Devi before migration scoping begins. If Devi has an API, we attempt a read-only connection to enumerate the object list and field schemas. If only CSV export is available, the customer provides it. If no export mechanism exists, we work from screenshots, internal spreadsheets, or database snapshots the customer can compile. The discovery phase output is a written data model document listing every object, field, field type, and sample values found in the export. No migration scope is confirmed until this document is reviewed and signed off.

Schema design and GoHighLevel setup

We design the GoHighLevel destination schema based on the discovery export. This includes configuring standard Contacts and any required custom objects, recreating custom fields with GoHighLevel field types, setting up Opportunity Pipelines and Stages to reflect Devi's lead lifecycle, and establishing the contact-account relationship. The schema is deployed into a GoHighLevel sub-account (or Sandbox-equivalent if available) for validation before production migration begins.

Mapping design and owner reconciliation

We design the field-level mapping from Devi's export fields to GoHighLevel fields, resolving any type mismatches (e.g., date formats, picklist values, numeric precision). We extract every distinct owner or assignee from the Devi export and match by email against the destination GoHighLevel account's User table. Any owner without a matching User goes to a reconciliation queue for the customer's admin to provision. Migration cannot proceed past this step because OwnerId references are required on most GoHighLevel standard objects.

Sandbox migration and reconciliation

If GoHighLevel's sub-account model supports a staging environment, we run a full migration into it using production-like data volume. The customer reconciles record counts, spot-checks 25-50 random records against the Devi source data, and signs off the mapping before production migration begins. Any mapping corrections are applied here. If no staging environment is available, we run the migration in batches with a hold on live data until reconciliation is complete.

Production migration in dependency order

We run production migration in record-dependency order: Users (manual provisioning confirmed), Accounts (if applicable from Devi's company data), Contacts (with AccountId resolved), any Custom Objects (with Contact lookup resolved), and files or attachments (AI-generated content assets from Devi). Each phase emits a row-count reconciliation report before the next phase begins. We use GoHighLevel's Bulk API where applicable for large record sets, with chunking and retry logic on rate-limit responses.

Cutover, validation, and automation rebuild handoff

We freeze any active Devi usage that could create delta records during cutover, run a final delta migration of any records modified during the migration window, then confirm GoHighLevel as the system of record. We deliver the automation inventory document to the customer's admin. We support a one-week hypercare window where we resolve any reconciliation issues. Workflow rebuild, email authentication setup, and admin training are outside the standard migration scope and are handled as separate engagements.