Migrate from Oncord to HubSpot

Oncord contacts migrate as HubSpot contacts. Email address is the primary deduplication key. Owner resolution maps Oncord user email to HubSpot owner by email match. Contacts without a company link land in HubSpot as unassociated contacts and can be linked post-migration.

Oncord companies migrate as HubSpot companies. Domain field maps to the website property. Parent-child company relationships in Oncord are preserved using HubSpot's parent company association. Multi-company contacts collapse to a primary company with secondary associations surfaced as additional company links.

Oncord deals migrate as HubSpot deals. Each deal carries its name, amount, stage label, close date, owner, and associated contact and company links. The dealstage value is stored as a custom pick-list in HubSpot rather than a native pipeline-stage because Oncord does not enforce a pipeline model.

Oncord products migrate as HubSpot products. If Oncord products are directly linked to deals with pricing, they create HubSpot Line Items connected to the corresponding deal. Variant data (size, colour) in Oncord maps to a HubSpot custom property on the product record.

Oncord Groups are exported as HubSpot static Lists, preserving every member contact present at cutover. Because HubSpot lists can be static or dynamic, we document the group membership criteria—including any inclusion rules and tag conditions—so your team can optionally recreate groups as HubSpot dynamic lists using property-based filters post-migration.

Oncord email logs (sent, opened, clicked) migrate as HubSpot engagements with type='EMAIL', preserving the original send timestamp, recipient address, and all associated contact and deal links. Any open/click tracking metadata is stored in custom engagement properties, and the email body content—including HTML formatting—migrates into the HubSpot engagement note field. Attachments are referenced by URL or re-uploaded if stored within Oncord.

Oncord call records—including duration, direction, and outcome—migrate as HubSpot engagements with type='CALL', preserving the original call start time and linking each engagement to the relevant contact and deal. Call disposition and any free-text notes from Oncord map to HubSpot's call outcome and body fields. If Oncord stored a call recording URL, that reference is attached as a custom property on the engagement.

Oncord meeting records—including title, start/end time, invitee list, and any location or description—migrate as HubSpot meetings, preserving the original start and end timestamps and linking each meeting to its associated contact and deal records. Attendee information is transferred as meeting participants, and recurrence patterns are noted in a custom field for manual rebuild in HubSpot's calendar tools if needed.

Oncord notes are migrated as HubSpot engagements with type='NOTE', preserving the original creation date and any rich-text formatting that the source data supports. Plain-text fallback is applied when HTML or styled content cannot be reliably converted. Attachments linked to a note are referenced via URL in the engagement, and any internal tags or categories are recorded in a custom property for downstream filtering.

Oncord custom fields on contacts are created as HubSpot custom contact properties prior to the migration load. Field type mapping translates Oncord text fields to HubSpot string properties, numeric fields to number properties, date fields to date properties, and pick-list fields to enumeration properties with each value mirrored. Field-level visibility and form-display settings are not transferred and must be reconfigured in HubSpot's property settings.

Oncord custom fields on deals are created as HubSpot deal properties before migration. Each field is mapped according to its type: text to string, numbers to number, dates to date, and pick-lists to enumerations with values mirrored one-to-one. Default values are noted in a custom field metadata file, but visibility and form-display settings are not migrated and must be set in HubSpot after the load.

Oncord users are resolved by email against HubSpot owners, using the email address as the unique key. Any Oncord user without a matching HubSpot email is flagged before migration, allowing your team to decide whether to create a new HubSpot seat or reassign their records to a fallback owner. Note that HubSpot seat licensing determines record visibility, so only users with active seats can own records after the load.