Migrate from PipeRun CRM de Vendas to HubSpot

PipeRun contacts map directly to HubSpot contacts using email as the primary key for deduplication during migration. The contact's primary company association in PipeRun translates to the HubSpot company association via the Contact-Company association object. Contacts without a company assignment import cleanly without a company link. When contacts have multiple company associations in PipeRun, the most recently modified association becomes the primary HubSpot company link.

PipeRun's lead status values (novo, qualificado, em negociação, etc.) translate into HubSpot's lifecycle_stage property. Closed-won PipeRun deals force the linked contact to lifecycle_stage = 'customer'. Closed-lost leaves the contact at its last stage. PipeRun lead-status values are preserved as a custom property for audit continuity.

PipeRun companies map to HubSpot companies with direct field-name correspondence on standard properties. Parent-company hierarchies in PipeRun map to HubSpot's parent-company field. Multi-company contacts collapse to one primary HubSpot company association; additional companies appear as secondary associations on the contact.

PipeRun deals map to HubSpot deals. Each deal's linked contact and company associations are recreated using HubSpot's association API. Deal value is stored as the Amount field in the deal's currency. FlitStack flags any PipeRun deal linked to multiple contacts so all associations can be confirmed before the full run.

Each PipeRun funnel translates to a separate HubSpot pipeline with independent stage pick-lists scoped to that pipeline. PipeRun's funnel stages map to HubSpot pipeline stages. The original PipeRun funnel name and stage-enter timestamps are preserved as HubSpot custom properties (funnel_name__c, stage_entered_at__c) to maintain historical reporting continuity within HubSpot reports and dashboards.

PipeRun call, email, and meeting records migrate as HubSpot engagements with original timestamps and owner attribution preserved. Each engagement is linked to its parent contact or deal via HubSpot's association model. Engagement type maps to the engagement type field in HubSpot's data.

PipeRun notes migrate as HubSpot notes attached to their parent contact, company, or deal record. The complete note body text is preserved verbatim during migration. PipeRun file attachments on notes are downloaded from the source system, re-uploaded to HubSpot Files, and then linked to the corresponding note record in HubSpot for complete attachment continuity.

PipeRun users are matched to HubSpot users by email address. Unmatched users are flagged in the migration report with a fallback owner assigned. Contacts and deals owned by unmatched users land under the fallback owner so no record is orphaned during migration.

PipeRun proposals with ICP-Brasil e-signature have no HubSpot native equivalent. The proposal content, line items, and status are preserved as a HubSpot custom object so the historical record is accessible. E-signature status cannot be replicated; the document body migrates as a reference attachment.

Any PipeRun field that is not a standard property maps to a HubSpot custom property. The custom property type in HubSpot is chosen based on the source data type (text, number, date, picklist). PipeRun picklist values are migrated as HubSpot picklist options with a value-by-value mapping.

PipeRun integrations including WhatsApp via PipeRun MAX, RD Station, MailChimp, and Superlógica represent third-party connections that cannot be structurally exported during migration. We document each active integration for the team to manually rebuild inside HubSpot or through integration platforms like Zapier or Make.

PipeRun automations (ação automática) are workflow definitions with trigger-action logic that have no HubSpot structural equivalent. FlitStack exports the automation definitions as a JSON reference document that a HubSpot admin can use to rebuild equivalent workflows in HubSpot's Automation section.