Migrate from Customer Database App to HighLevel

Customer Database App Contacts map directly to GoHighLevel Contacts. Every exported CSV column becomes a field in GoHighLevel — standard fields (name, phone, email, address) map to their GoHighLevel equivalents; user-defined custom fields are pre-created in GoHighLevel before import so the CSV column headers have a matching destination field to write into. We infer the active field set from the first export file's column headers, flag any columns that do not yet exist in GoHighLevel, and the customer's admin creates the corresponding custom fields before we proceed with data load.

All user-defined fields from Customer Database App become GoHighLevel custom fields. Field type inference is based on the data values in the export — numeric strings become number fields, dates become date fields, yes/no strings become checkbox fields, and free-text fields become text fields. Comma-delimited values within a custom field are flagged and optionally split into tag records in GoHighLevel. We do not apply any automated type casting that would truncate or corrupt data; the admin reviews the type assignments during scoping before they are created in GoHighLevel.

Customer Database App's Kanban pipeline stages are stored as a label value on each contact record. We extract the unique stage names from the exported dataset, create a corresponding GoHighLevel Pipeline with matching stage labels, and map each contact's stage assignment to the appropriate stage in the new pipeline. If the customer has used multiple named pipelines in Customer Database App, each one becomes a separate GoHighLevel Pipeline with its own stage configuration.

Customer Database App exports groups and tags as comma-separated strings within a field on each contact record. We split these into individual tag labels and apply them to the corresponding GoHighLevel Contact records. Tags that do not yet exist in GoHighLevel are created during import. The tag values are preserved verbatim; no renaming or normalization is applied unless the customer requests it during scoping.

Birthday dates export from Customer Database App as a standard date column. We map this to a GoHighLevel custom date field named Birthday. If the customer prefers, we can map it to a dedicated birthday or anniversary field in GoHighLevel if one exists in their account. The date format in the CSV is normalized to ISO 8601 before import to avoid format mismatches.

Customer Database App does not have a standalone Companies object — company information is stored as a free-text field on the contact record. We map this to the Company field on the GoHighLevel Contact. If the customer wants to use GoHighLevel's separate Company model, we can create a Company record per unique company name and link the Contact to it as a 1:N relationship, but this requires the customer to confirm whether the existing company data is rich enough to justify the split.

Contact images and PDF exports of individual Customer Database App records can be bundled into a ZIP archive alongside the CSV. We map each contact's image or PDF to the corresponding GoHighLevel Contact attachment field. Large attachments over GoHighLevel's file size limits are flagged and the customer decides whether to upload them manually post-migration or store them in a linked Google Drive or Dropbox folder with the URL recorded as a custom field.

Vouchers are a standalone object in Customer Database App with no direct equivalent in GoHighLevel's standard CRM model. Voucher balances are not exported via CSV and cannot be recovered through the app's export function. We do not migrate voucher data. We recommend exporting any voucher records as a separate supplemental CSV for manual re-entry in GoHighLevel or a dedicated voucher management tool if the customer's business relies on voucher tracking.