Migrate from Kordeva to HighLevel

Kordeva Contact records map directly to GoHighLevel Contact. Standard fields (name, email, phone, address) are well-documented in Kordeva's CRM and import cleanly. Custom field attributes retrieved via Kordeva's Custom Fields API migrate to GoHighLevel custom fields, which are available on all standard objects without requiring a separate custom object setup. We enumerate all custom field definitions during discovery and carry them through as GoHighLevel custom properties.

Kordeva Company records map to GoHighLevel Contact records of type Organization. The company name becomes the Contact's company name field, and we create an Organization-type Contact before any Person-type Contacts are imported so that the company-contact association is preserved. Any custom company-level attributes from Kordeva migrate as GoHighLevel custom fields on the Organization Contact record.

Kordeva Deal records map to GoHighLevel Opportunities. Pipeline stage names and deal amounts transfer directly. Stage configuration (stage-to-stage mapping) requires customer review because Kordeva's pipeline layout may not match GoHighLevel's default Opportunity stages. We recreate the destination pipeline in GoHighLevel with stages mapped to the customer's existing Kordeva stage names during the configuration phase before any deal records import.

Each Kordeva pipeline maps to a GoHighLevel Pipeline with corresponding stages. We configure the GoHighLevel pipeline stages before migration begins, matching Kordeva's stage names and probabilities. GoHighLevel's visual pipeline builder lets us replicate the Kordeva stage layout, including any custom stage colors or probability percentages, during the pre-migration configuration phase.

Kordeva activity records (calls, emails, tasks, meetings) logged against contacts and deals migrate to GoHighLevel's activity timeline. Call logs transfer as GoHighLevel Call Log records with duration, disposition, and timestamp preserved. We link each call log to the correct Contact record using the email address or phone number as the dedupe key.

Kordeva email activity records migrate to GoHighLevel Email records attached to the corresponding Contact. Email subject, body, direction (sent/received), and timestamp transfer. We flag that GoHighLevel's email infrastructure (LC Email via Mailgun) uses shared IP reputation and advise the customer on warm-up best practices post-migration, particularly if high email volume is expected.

Kordeva task records migrate to GoHighLevel Task records with status, priority, due date, and assigned user preserved. Task assignment resolves by matching Kordeva owner email to the GoHighLevel user email during migration. Any task associated with a deal links to the corresponding GoHighLevel Opportunity record.

Kordeva meeting records migrate to GoHighLevel Appointment records with date, duration, location, and attendee list preserved. Attendee emails are resolved against the GoHighLevel Contact table during import. If an attendee contact does not exist in GoHighLevel, we create a minimal Contact record to preserve the meeting attendee reference.

Kordeva's Custom Fields API provides the schema for extended resource attributes. We enumerate all custom field definitions during discovery, including field type, required flag, and any picklist values for dropdown fields. Each custom field is recreated as a GoHighLevel custom field on the appropriate object (Contact, Organization, Opportunity) before any data import begins. Custom field values then migrate as part of the standard record import.

Kordeva Owner records (the user assigned to contacts, companies, and deals) map to GoHighLevel User accounts. We match owners by email address during migration. Any Kordeva Owner without a matching GoHighLevel User account is held in a reconciliation queue for the customer to provision before record import continues, because OwnerId references are required on most standard GoHighLevel objects.