Migrate from Onpipeline to HighLevel

Onpipeline Contacts migrate to GoHighLevel Contacts with all standard fields (name, email, phone, address) and custom fields preserved. The GoHighLevel Contact record becomes the primary person record and the anchor for Opportunity associations. We map Tags to GoHighLevel Tags (multi-checkbox on Contact) and preserve Lifecycle Stage as a Contact custom field if it exists in the source schema.

Onpipeline Company records migrate to GoHighLevel Organizations. The Organization record holds organizational data and links to multiple Contacts. We maintain the Contact-to-Company linkage in GoHighLevel by resolving the Organization lookup on each Contact record during import. Company domain becomes the Organization Website field and is used as the dedupe key.

Onpipeline Deals migrate to GoHighLevel Opportunities. The Deal value, stage assignment, probability, and custom fields transfer directly. We resolve the linked Contact as the GoHighLevel Opportunity Contact lookup and the linked Company as the Organization lookup before inserting. Deal name becomes Opportunity name, and the original Onpipeline deal ID is preserved in a custom field for audit.

Onpipeline custom stage names and probabilities per pipeline map to GoHighLevel Pipeline stage names and probabilities. We capture the full stage hierarchy and configure GoHighLevel Pipelines with matching stage values before Opportunity import so that stage assignments resolve correctly at migration time.

Onpipeline Events (calendar appointments) migrate to GoHighLevel Calendar Events with datetime, duration, assigned user, and description preserved. Tasks and Notes migrate as Tasks with the activity body in the Task notes field. Each Activity inherits the Contact or Deal association from the source. Owner assignment is resolved by email match to GoHighLevel users.

Onpipeline Products (name, price, SKU, stock quantity) migrate to GoHighLevel Products. We preserve SKU as the product code, price as the base price, and stock quantity where GoHighLevel supports inventory tracking. Products become available for line item association with Opportunities.

Onpipeline Quotes migrate to GoHighLevel Opportunities with Line Items. The Quote header (contact reference, deal reference, pricing, status) becomes the Opportunity. Each Quote line item becomes an Opportunity Line Item linked to the Product. E-signature status is preserved as a custom field on the Opportunity. We resolve parent Contact and Organization lookups before inserting.

Onpipeline Invoices migrate to GoHighLevel Invoices with headers, line items, and payment status. Invoices generated from Deals inherit the Opportunity association. Recurring invoice configurations are noted as a custom field set in GoHighLevel but require manual setup of recurring profile automation post-migration since the automated recurring schedule does not transfer.

Onpipeline custom fields on Contacts, Companies, Deals, and Products migrate to GoHighLevel custom fields. We determine whether each field belongs on a Contact custom field or an Opportunity custom field based on its source object association. Note that GoHighLevel enforces this distinction at field creation and does not allow conversion afterward, so we confirm the object scope with the customer during scoping before creating fields.

Onpipeline Users are assigned as Deal owners and activity assignees. We map each Onpipeline User to a corresponding GoHighLevel User by email match. Any Onpipeline User without a matching GoHighLevel User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Onpipeline Tags applied across Contacts, Companies, and Deals migrate to GoHighLevel Tags. We preserve multi-tag assignments per record. Tags used for segmentation migrate as Contact tags or Opportunity tags depending on the object they are attached to in Onpipeline.

Onpipeline Recurring Revenue records (subscription schedules) migrate as GoHighLevel Recurring Profiles with metadata and schedule preserved. Automated recurring invoice generation does not transfer as active automation. We document the schedule configuration for manual setup in GoHighLevel and note that automated generation requires either a workflow rebuild or a plan feature confirmation.