Migrate from Verenia to HubSpot

Verenia person records map directly to HubSpot Contacts. Name, email, phone, job title, and address fields migrate as-is with straightforward field-to-field correspondence. Owner resolution uses email address as the matching key against HubSpot user records — when an exact email match is found, the HubSpot user becomes the record owner. Unmatched owners are flagged for manual assignment before the migration commits, ensuring every record lands with a valid HubSpot owner and no orphaned records enter the system.

Verenia company records map to HubSpot Companies with a 1:1 relationship for name, domain, industry, and employee count fields. Parent-company hierarchies in Verenia map to HubSpot's parent company association. Multi-company contacts collapse to one primary company association with additional companies surfaced as secondary associations.

Verenia quote headers (quote number, total amount, status, created date, owner) map to HubSpot Deals. Quote status drives both Deal stage and HubSpot lifecycle stage assignment: Closed Won → Customer, Open → Lead or SQL. The original quote number is preserved as a custom field for audit traceability.

Verenia quote lines (product name, quantity, unit price, discount, line total) are split across HubSpot Deal fields when lines are few. When quotes have many line items or complex configurations, we create a Quote Line Items Custom Object linked to the Deal via association — your admin chooses the approach during planning.

Verenia product catalog items map to HubSpot Products. Product name, SKU, description, cost, and base price transfer directly. Volume pricing tiers and configuration constraints from Verenia are preserved as custom fields on the HubSpot Product since HubSpot Products do not natively support rule-based guided configuration.

Verenia guided-configuration bundles (multi-option product rules, conditional constraints, optional components) have no native HubSpot equivalent. We preserve the configuration snapshot as a JSON or delimited string in a custom field on the HubSpot Product or as a Custom Object record. Rebuild guidance is exported for your admin.

Verenia order records map to closed HubSpot Deals. When orders contain fulfillment tracking or shipping data not captured in Deal fields, we create an Order Custom Object linked to the Deal. Order number, fulfillment status, and ship date are preserved for customer service continuity.

Verenia volume discount tiers and customer-specific pricing rules are stored as custom fields on the HubSpot Product (Volume_Discount_Rule__c, Customer_Specific_Price__c). Since HubSpot Products do not evaluate rules at quote time, these fields serve as reference data for your CPQ rebuild or sales team manual entry.

Verenia attachments on quotes (proposals, PDFs, spec sheets) are downloaded and re-uploaded to HubSpot Files linked to the corresponding Deal or Product record. File size limits per HubSpot apply — files over 25MB are split or linked by URL reference.

Verenia custom fields on contacts, accounts, quotes, or products migrate as HubSpot custom properties. We map field type (text, number, date, picklist) and preserve the original field label in a migration audit log so your admin can rename properties to HubSpot naming conventions post-migration.

Verenia user records are matched to HubSpot users by email address. Inactive Verenia users who do not have HubSpot accounts are assigned to a fallback owner. Ownership of CRM records (contacts, companies, deals) is resolved after user matching — unresolvable owners are flagged before migration.