Migrate from Pega Sales Automation to HubSpot

Pega contacts migrate to HubSpot contacts with first name, last name, email, phone, job title, and address fields preserved directly. The Pega contact's pyStatusWork and operator assignment fields are not HubSpot-native and require custom field creation or manual reassignment in HubSpot post-migration.

Pega Organizations map directly to HubSpot Companies. Pega parent-child hierarchy (pyOrganizations parent field) maps to HubSpot's Parent Company lookup. Organizations with multiple contacts in Pega become a single Company in HubSpot with N contacts associated. Circular organization references are flagged before migration commits.

Pega Opportunities with pyAmount, pyProbability, pySalesStage, and close date map directly to HubSpot Deals. The Pega opportunity name becomes the HubSpot deal name. Deal owner resolves via email match from Pega operator to HubSpot user. Pega's AI-driven next-best-action guidance does not transfer — that context is lost and must be rebuilt manually.

Pega Tasks (assignments with subject, status, and due date) map to HubSpot Tasks with Subject, Status, and HubSpot owner resolved by email. Pega's operator assignment (pxAssignedOperator) resolves by email match to HubSpot owner. Task create and modify timestamps are preserved as custom datetime fields in HubSpot.

Pega Cases map to HubSpot Tickets with Pega's pyCategory, pyStatusWork, and pyUrgencyAssign maps to HubSpot's ticket status, priority, and source fields. Pega case resolution notes (pyResolution) map to HubSpot ticket body or a custom text field. Pega case ID preserved as a custom field for traceability.

Pega custom properties (fields added beyond the standard entity schema) require HubSpot custom property creation before data lands. Pega text, number, date, and pick-list property types map to HubSpot's equivalent types. We deliver a custom property creation plan as part of the pre-migration schema setup so HubSpot is ready before validation runs.

Pega opportunity-to-contact associations migrate as HubSpot deal-to-contact associations. The primary contact on the Pega Opportunity becomes the primary association in HubSpot. Additional contacts on the opportunity link to the same deal in HubSpot via the deal-contact association model. If multiple contacts share the same role on the opportunity, each receives its own association entry, preserving role information as a custom property on the association when available.

Pega file attachments on contacts, organizations, opportunities, and cases are downloaded and re-uploaded to HubSpot Files, re-associated with the target record. File size limits apply per HubSpot's 25MB per-file default. Inline images in case notes are extracted and rehosted as HubSpot file attachments.

Pega operators (pxAssignedOperator, pyModifiedBy, pxCreateOperator) resolve to HubSpot owners by email match. Unmatched operators are flagged before migration — your team either invites them to HubSpot first or assigns their records to a fallback owner. Historical operator attribution is preserved as a custom field for audit purposes.

Pega's next-best-action guidance, AI coaching agents, and decisioning rules are AI-platform constructs that live in Pega's Customer Decision Hub. HubSpot has no equivalent — these must be redesigned from scratch in HubSpot's workflow tools or Breeze AI features. We document the Pega rule structure as a reference for your HubSpot admin.