Migrate from SuiteCRM to HighLevel

SuiteCRM Accounts map to GoHighLevel Contacts with the company name stored in the contact record and the original Account ID preserved in a custom field for reference. GoHighLevel does not have a separate Account object; all company data attaches to the Contact. We tag the contact with the original Account industry and website so that company-level context is searchable within GoHighLevel's contact records.

SuiteCRM Contacts map directly to GoHighLevel Contacts with standard fields (name, email, phone, title) preserved. Custom fields added via Studio migrate to GoHighLevel custom fields, which must be pre-created before import. We validate field types during scoping — date fields, dropdowns, and text fields each have different GoHighLevel type equivalents. The primary Account link from SuiteCRM is preserved as a tag on the GoHighLevel Contact.

SuiteCRM Leads do not have a direct GoHighLevel equivalent because GoHighLevel does not have a separate Lead object. All leads are imported as Contacts with a lead_source tag and status tag carrying the original SuiteCRM lead_status value. We compute the merge at migration time and flag any Lead-specific fields (e.g., lead_score, status) that require custom GoHighLevel fields pre-created before import.

SuiteCRM Opportunities map to GoHighLevel Opportunities with revenue amount, close date, and sales stage preserved. The GoHighLevel pipeline and stages are configured before migration based on the customer's SuiteCRM sales stage values. Closed-Lost and Closed-Won status map to GoHighLevel Won/Lost pipeline stages. The parent Account link is preserved as a tag on the GoHighLevel Opportunity.

SuiteCRM Products map to GoHighLevel Products if the product catalogue is used in quotes or opportunities. For product-heavy migrations (over 500 products), we recommend pre-creating the product list in GoHighLevel before importing Opportunities so that line-item references resolve correctly. Products without an Opportunity relationship can be stored as a Custom Object if the customer prefers.

GoHighLevel does not have a native Quote object with PDF generation and e-signature as standard CRM features. We map SuiteCRM Quotes to a Custom Object named Quote with line items, totals, and related Opportunity linkage stored as custom fields. The customer should evaluate GoHighLevel's document and e-signature integrations (DocuSign, PandaDoc) post-migration for the full quoting workflow.

SuiteCRM Invoices map to a Custom Object named Invoice. SuiteCRM tracks payment status (Paid/Unpaid) but lacks any AR ledger. We preserve the invoice amount, status, and date fields. The customer must source the financial reconciliation layer from their accounting system because GoHighLevel has no native accounting module and SuiteCRM Invoice records do not include ledger entries.

SuiteCRM Contracts (with start/end dates and renewal status) map to a Custom Object named Contract. Renewal date fields are preserved as date types. We attach the related Contact via a lookup relationship if the GoHighLevel plan supports relationship fields on Custom Objects.

SuiteCRM Cases (tracked in the Bugs module) have no direct GoHighLevel equivalent. For support-track migrations, we recommend a Custom Object named Case with status, priority, and description fields. For sales-track organizations, Cases may be better represented as Opportunities with a custom status field. The customer chooses the representation during scoping.

SuiteCRM Campaigns have no GoHighLevel equivalent as a first-class object. Campaign target list memberships migrate as tags on the relevant Contacts. Campaign response activity (opens, clicks) migrates as notes on the Contact record. For ongoing campaign management, we recommend GoHighLevel's Workflows as the replacement automation tool, documented in the handoff package.

SuiteCRM Documents store files on the server filesystem (typically /upload/) with metadata in the database. We extract the file blobs alongside database records and re-upload them as file attachments on the corresponding GoHighLevel Contact record. File system permission preservation is critical during extraction; we validate file integrity checksums after extraction and before upload. Documents without a parent Contact are held in a reconciliation queue.

SuiteCRM Studio custom fields store in extended database tables with a naming convention appended to the module name. We scan the database schema during discovery, identify all custom field definitions, and pre-create the corresponding GoHighLevel custom fields before record import. Field type mapping (dropdown, date, checkbox, text) is validated against GoHighLevel's supported types. Custom fields with conditional visibility rules in SuiteCRM do not migrate those rules.