Migrate from ASPEC to HighLevel

Scoping and export method confirmation

We conduct a discovery call to map the ASPEC data landscape: record counts by object (Contacts, Companies, Opportunities, Activities), active custom fields and their types, pipeline stage definitions, tagging taxonomy, and user/owner list. We confirm the export method (manual UI export, database-level access, or a combination) and validate that the customer has access to all required data exports. If database-level access is available, we extract directly; if not, we coordinate a paginated manual export and validate completeness against record counts. The scoping output is a written migration scope document with record counts, field mappings, and a confirmed export method.

Schema discovery on ASPEC

We enumerate all active ASPEC custom field definitions across Contact, Company, and Opportunity objects, capturing field names, data types (text, number, date, dropdown, checkbox, multi-select), and conditional visibility rules. We capture the full ASPEC pipeline configuration: stage names, stage order, and any probability or probability mapping. We document the tagging taxonomy and any tag-to-segment logic. This discovery step is mandatory for ASPEC migrations because custom field definitions are not embedded in record exports; without this step, custom fields are silently dropped during GoHighLevel import.

GoHighLevel schema provisioning

We create the destination schema in GoHighLevel before any data import. This includes provisioning custom fields on Contact, Company, and Opportunity objects to match the ASPEC custom field definitions captured during schema discovery. We configure the GoHighLevel pipeline with stage names mapped from ASPEC, and set stage probabilities. We create GoHighLevel Users for each ASPEC owner (the customer provisions the actual User accounts and provides the GoHighLevel User IDs). We document the GoHighLevel schema for customer sign-off before import begins.

Test migration into GoHighLevel sandbox

We run a full test migration into a GoHighLevel test environment using production-like data volume. The customer reconciles record counts, spot-checks 20-30 random Contact, Company, and Opportunity records against the ASPEC source, and validates that custom field values populated correctly. We identify and correct any mapping issues, incorrect field types, or truncated values during this phase. GoHighLevel does not have a formal sandbox for all tiers, so we use a separate sub-account or test environment if available. The customer signs off on the test migration before production migration begins.

Production migration in dependency order

We run production migration in record-dependency order: GoHighLevel Users validated (customer-provisioned), Companies from ASPEC (standalone, no dependencies), Contacts with CompanyId resolved, Opportunities with ContactId and OwnerId resolved, Activity history (Tasks, Events) linked to Contacts or Companies, Tags applied to Contact and Company records. Each phase emits a row-count reconciliation report. ASPEC's lack of a bulk API means we process records in batches compatible with GoHighLevel's API rate limits, using exponential backoff on 429 responses.

Cutover, validation, and automation handoff

We freeze ASPEC record writes during cutover, run a final delta migration of any records modified during the migration window, and validate final record counts against the ASPEC source. We deliver a written automation inventory documenting any ASPEC automation logic discovered during schema audit, mapped to GoHighLevel Workflow equivalents for the customer's admin to rebuild. We provide a reconciliation report with record counts by object, open items list, and a post-migration checklist covering User activation, pipeline stage validation, and email sending domain configuration. We offer a one-week hypercare window for reconciliation issues; workflow rebuild and training are separate engagements.