Migrate from PipeRun CRM de Vendas to HighLevel

PipeRun Contacts migrate to GoHighLevel Contacts with name, email, phone, and address fields preserved. We map PipeRun contact custom fields to GoHighLevel Contact custom fields, which must be pre-created in GoHighLevel before import. The GoHighLevel Contact ID is captured after insert and used as the parent reference for any imported Activities linked to that Contact.

PipeRun Companies migrate to the Company section within GoHighLevel Contacts. Where PipeRun stores a separate Company record, GoHighLevel embeds company data as a typed block within the Contact record. If the destination GoHighLevel sub-account uses a separate Company object via an integration, we map accordingly during scoping. Company ownership from PipeRun maps to the assigned Contact owner in GoHighLevel.

PipeRun Deals migrate to GoHighLevel Opportunities. Each Deal's Funnel assignment and Pipeline Stage (Etapa) are preserved by mapping the Funnel to a GoHighLevel Pipeline and the stage order to GoHighLevel stage values. Deal value, expected close date, and owner all migrate directly. If a PipeRun Deal has no assigned Funnel, we attach it to a default Pipeline configured during schema setup.

Each PipeRun Funnel maps to a separate GoHighLevel Pipeline. We extract all Funnel definitions and their stage order from PipeRun's admin settings before migration begins. GoHighLevel Pipelines are created with stage names matching the PipeRun stage labels and in the same sequence order. Stages with no deals are still created to preserve the full process definition. If PipeRun has one Funnel, it maps to one Pipeline.

PipeRun Activity records (calls, emails, meetings, notes) migrate to GoHighLevel Activity records linked to the parent Contact or Opportunity. We resolve the parent GoHighLevel Contact ID at migration time using the ID mapping table built during the Contact phase. Long free-text notes are preserved; if truncation occurs, we flag it in the reconciliation report. Activity timestamps migrate as-is to preserve the engagement timeline.

PipeRun Proposals carry line items, pricing, and e-signature status. GoHighLevel does not have a native Proposals object as a standalone record type in the standard CRM. We migrate proposal content and line item data as a GoHighLevel Opportunity with a custom field capturing the proposal value and status, and we upload the proposal PDF as a GoHighLevel document attached to the Opportunity. Electronic signature status (signed, pending, expired) is preserved as a custom field value. Customers who rely heavily on PipeRun's native CPQ may need GoHighLevel's Documents feature or a separate quoting tool.

PipeRun custom fields on Contacts, Companies, Deals, and Activities migrate to GoHighLevel Contact custom fields or Opportunity custom fields depending on which object they are attached to in PipeRun. GoHighLevel enforces a strict separation between Contact-level and Opportunity-level custom fields, and this assignment cannot be changed after field creation. We pre-create all destination fields before migration, assign them to the correct folder (Contact or Opportunity), and map field types (text, date, dropdown, currency) to their GoHighLevel equivalents.

PipeRun Users assigned as Deal Owners and Activity owners map to GoHighLevel User accounts. We resolve owners by email match against the destination GoHighLevel sub-account's user list. Any PipeRun User without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive PipeRun users who owned historical records are migrated as inactive GoHighLevel users so that ownership attribution is preserved.

Files and attachments linked to PipeRun Deals or Proposals are batch-downloaded from the web interface and re-uploaded as GoHighLevel Documents attached to the corresponding Opportunity or Contact. File naming conventions are preserved and folder structure is replicated where possible. Files without a clear parent record are archived under a root-level migration folder.

PipeRun tags applied to Deals and Contacts migrate to GoHighLevel Tags. Tags are imported as a multi-select string value and assigned to the corresponding Contact or Opportunity record. If GoHighLevel's native tag functionality is not enabled on the destination sub-account, tags are mapped to a multi-select custom field instead.

PipeRun's workflow automation rules (ações automáticas) are platform-internal triggers with no export mechanism. We do not migrate them. We deliver a written inventory of every active PipeRun automation with its trigger conditions, actions, and field dependencies, plus a recommendation for the equivalent GoHighLevel Workflow builder configuration. The customer's admin rebuilds these in GoHighLevel post-migration.

WhatsApp conversations managed through PipeRun MAX are stored in PipeRun's messaging layer and are not accessible via export. Only metadata such as conversation timestamps and participant identifiers are recoverable. We flag this upfront and recommend the customer archive WhatsApp chat exports separately before migration begins. Conversation metadata can be recorded as a GoHighLevel Activity note if the customer chooses.