Migrate from webCRM to HighLevel

webCRM Organisations map to GoHighLevel Companies. Organisation name becomes Company name; address, phone, and website fields map directly. We use Organisation ID as the dedupe key during import and preserve the Organisation ID in a custom text field webcrm_id__c on the Company record for audit traceability. Organisation custom fields migrate as Company custom fields.

webCRM Contacts map to GoHighLevel Contacts. The Contact-Organisation link migrates as a Company lookup on the Contact record, resolved by matching the Contact's Organisation ID or name against the imported Companies. Email, phone, name, and address fields map directly. Contact custom fields migrate as GoHighLevel Contact custom fields. webCRM contact status (Active/Inactive) maps to a GoHighLevel contact tag or a custom status field.

webCRM Deals map to GoHighLevel Opportunities. The Deal-Organisation link becomes Opportunity-Company lookup, and Deal-Contact link becomes Opportunity-Contact lookup (we attach the primary Contact from the Deal if multiple exist). Deal value maps to Opportunity value; deal stage name maps to the matching GoHighLevel pipeline stage. webCRM pipeline assignments map to GoHighLevel pipeline and stage names configured during schema setup.

webCRM Deliveries are exported as nested XML via Zynk with header fields (customer, date, total) and line-item detail (product, quantity, price). We parse the XML into a flat structure: Order as the header record and Order Items as child line records. The Order links to the Contact and Company; Order Items link to the Order and to GoHighLevel Product records. This split is necessary because GoHighLevel separates order headers from line items rather than nesting them inline.

webCRM Product Database entries map to GoHighLevel Products. Product name, SKU, price, and description map directly. We create Standard Price Book entries during import so that Products are available for Opportunities and Orders. If webCRM tracks inventory quantity, that field maps to a GoHighLevel custom field since Products in GoHighLevel do not natively carry real-time inventory unless connected to a third-party inventory integration.

webCRM Tasks map to GoHighLevel Tasks attached to the Contact or Company record. Task subject, due date, status, and assigned owner migrate. webCRM task priority maps to GoHighLevel task priority. Task notes migrate as the task description field. Tasks linked to specific Contacts carry the Contact lookup; tasks linked to Organisations carry the Company lookup.

webCRM Automation Rules are not accessible via export and cannot be migrated as code. We identify every active automation during scoping and produce a written inventory with the automation name, trigger type (time-based, event-based, inactivity), conditions, and actions. The customer rebuilds these in GoHighLevel's workflow builder post-migration. Budget 1-2 hours per automation rule for straightforward time-delay sequences; more complex multi-branch automations require additional scoping.

webCRM custom fields on Organisations map to GoHighLevel custom fields on Companies. We extract the full custom field schema during scoping, including field type, picklist values, and required/optional status. GoHighLevel requires pre-creating custom fields before import, so we create the destination schema before loading any data. Multi-select picklist fields from webCRM map to GoHighLevel multi-select fields.

webCRM custom fields on Contacts map to GoHighLevel Contact custom fields. Note that GoHighLevel distinguishes between Contact custom fields and Opportunity custom fields as separate field types; a field cannot be both. During scoping we confirm which webCRM custom fields belong on Contact records versus Opportunity records for Deal-linked fields.

webCRM custom fields on Deals map to GoHighLevel Opportunity custom fields. These are created separately from Contact custom fields in GoHighLevel's custom field management. Pipeline-stage-specific fields (Deal probability, close reason, competitor info) map to Opportunity fields scoped to the relevant pipeline.