Migrate from openCRX to HubSpot

openCRX LegalEntity maps to HubSpot Company. LegalEntity.fullLegalName becomes Company name; primary postal address maps to company address fields. openCRX accounts without a legal name default to a placeholder for review before migration. If an account has multiple locations, the primary address populates the Company address fields, while secondary locations are stored as custom address entries or linked as association records. This ensures no address data is lost during import.

openCRX Contact maps 1:1 to HubSpot Contact. First name, last name, email, phone, job title, and postal addresses transfer directly. Contacts without email are flagged for manual review — HubSpot requires unique email per contact. Duplicate detection runs post-import to merge any records that share the same email address, ensuring data hygiene in the target system.

openCRX supports N:N contact-to-company relationships. HubSpot allows one primary company_id per contact. We migrate the most recently-modified openCRX association as primary; secondary companies surface as Company associations via HubSpot's association API. If multiple associations share the same timestamp, a deterministic tiebreaker (e.g., alphabetical order) selects the primary, ensuring consistent mapping.

openCRX Lead objects map to HubSpot Contacts with lifecycle_stage set to 'lead'. openCRX Lead.rating (Cold/Warm/Hot) maps to a HubSpot custom property since HubSpot has no direct rating field — use lead score or custom property for rating. During import, lifecycle_stage defaults to 'lead' for all openCRX Leads; the rating property is populated using the original rating value, and any missing rating defaults to 'unknown' for further qualification.

openCRX Opportunity maps to HubSpot Deal. Opportunity.name becomes Deal name; amount, close date, probability, and stage transfer. openCRX's Opportunity stage values map to HubSpot pipeline stage names per the configured deal pipeline. Owner resolution matches openCRX owner email to HubSpot user; unresolved owners flag records for manual assignment before go-live.

openCRX's Quote, SalesOrder, and Invoice all inherit from abstract Contract. HubSpot has no native quote/order/invoice objects at the CRM tier. We merge the most recent Quote/SalesOrder values into the Deal as custom properties; line items require a custom object setup plan for rebuilding.

openCRX Activity Tracker groups become HubSpot engagements. openCRX activities with type 'call' become HubSpot calls; 'email' becomes emails; 'meeting' becomes meetings. Time entries attach as note content. openCRX activity hierarchies flatten to a single engagement per activity, preserving the original timestamp and owner attribution. Missing activity types are imported as notes for later review.

openCRX Product and ProductBundle map to HubSpot Products. openCRX price list entries map to HubSpot product pricing with currency preserved in a custom property since HubSpot multi-currency is limited at the product level. Bundle components are imported as separate product variants, and any pricing rules are documented for rebuilding in HubSpot's product configuration.

openCRX Segments, Topics, and Workflow Processes do not migrate. These define event-driven alerts and subscription logic specific to openCRX's servlet-based Workflow Handler. We export the workflow definition as a reference document for rebuilding in HubSpot workflows. Your team will need to translate the event triggers, conditions, and actions into HubSpot's enrollment criteria and workflow steps manually.

openCRX DataBindings PropertySet fields (Custom!fieldName) map to HubSpot custom properties per entity. Each custom field requires HubSpot property creation before migration. Field type mapping: string→single-line text, number→number, date→date, picklist→single-option. We provide a property checklist with exact names, types, and pick-list options to streamline HubSpot setup.

openCRX document attachments migrate to HubSpot Files. Files are re-uploaded to HubSpot's file storage and linked to the parent record (contact, company, or deal). openCRX WebDAV file references require re-hosting since HubSpot uses its own file CDN. After upload, each file's HubSpot ID is recorded for audit and association mapping.