Migrate from Skyward CRM to HighLevel

Skyward CRM Contact records map directly to GoHighLevel Contact. Standard fields (name, email, phone, address) migrate as typed fields. We extract all contact records before any child records (Activities, Deal associations) to establish the base contact set. On cloud deployments, the UI export delivers contact records in CSV format; on-premise deployments, we query the contacts table directly for richer field coverage including soft-deleted records.

Skyward CRM separates Lead records from Contact records with distinct lifecycle stages. In GoHighLevel, all prospects live in the Contact object with lifecycle status tracked via a custom field or tag. We merge inbound Leads and existing Contacts into the unified GoHighLevel Contact model, preserving the original Skyward lifecycle stage as a Contact custom field (e.g., original_lifecycle_stage__c) for reporting continuity.

Skyward CRM Company records map to GoHighLevel Company. The Company object in GoHighLevel acts as the parent entity for associated Contacts, mirroring Skyward's contact-to-company association. We extract Companies first to establish foreign-key relationships before importing child Contact records and assigning Company lookups during the contact phase.

Skyward CRM Deals map to GoHighLevel Opportunities with the pipeline and stage values mapped via a stage-mapping table produced during scoping. GoHighLevel Opportunities attach to a Contact (Who) and optionally a Company (What), which requires the Contact and Company import to complete before Deals land in their final pipeline stages. Closed-won and closed-lost values migrate with the original deal value and close date preserved.

Skyward CRM allows full customization of pipeline stage names with no standardized stage set. During scoping we capture the complete pipeline configuration and produce an explicit stage-mapping table that maps each Skyward stage name to a corresponding GoHighLevel pipeline stage. Multi-stage pipelines with custom fields per stage require additional GoHighLevel Opportunity custom field creation before the deal import phase.

Skyward CRM Activities migrate to GoHighLevel Activity records linked to the Contact. Activity type (call, email, meeting, task) maps to GoHighLevel activity_type. Activity timestamps normalize to UTC. We preserve the original activity notes as the GoHighLevel Activity notes field. Activity import follows Contact and Company import to ensure parent-record lookup resolution succeeds at insert time.

Skyward CRM's partner management module stores partner entities with commission structure, partner type, and shared lead attribution fields that do not map to a native GoHighLevel object. We extract partner records into a staging table and map them to GoHighLevel Company records (for organizational partners) or Contact records (for individual partners), with commission-related fields migrated as Contact or Company custom fields. The customer selects the strategy during scoping based on how they use partner data.

Skyward CRM custom fields require manual discovery via the admin panel because no public metadata API exists. We enumerate every custom field on each object during scoping, then create equivalent fields in GoHighLevel. We resolve whether each Skyward custom field belongs on a GoHighLevel Contact custom field (attached to the person) or an Opportunity custom field (attached to the deal) before creating the GoHighLevel schema, because GoHighLevel locks this distinction at field creation and does not permit switching afterward.

Skyward CRM users assigned as record owners map to GoHighLevel Users by email match. We extract the full user roster during scoping and create a user mapping table. Any Skyward owner without a matching GoHighLevel User is flagged in the reconciliation queue for the customer's admin to provision before record import resumes, because OwnerId references are required on Opportunities and Activities.