Migrate from Kordeva to HubSpot

Kordeva contacts map directly to HubSpot contacts. The primary company association becomes the HubSpot contact's primary company property. If the Kordeva contact has no associated company, the contact lands in HubSpot without a primary company — manual association or company creation can be done post-migration.

Every Kordeva custom field on a contact becomes a HubSpot custom property. The property must be pre-created in HubSpot Settings > Properties > Contact properties before the import runs. FlitStack delivers a custom property creation checklist based on the Kordeva field inventory so your HubSpot admin can set types and labels in advance.

Kordeva companies map directly to HubSpot companies. Company name, domain, industry, employee count, and annual revenue map to their HubSpot equivalents. Parent-company hierarchies in Kordeva map to HubSpot's parent company field — the parent company must be migrated first to avoid broken references.

Kordeva company-level custom fields migrate to HubSpot company custom properties. Like contact properties, these require pre-creation in HubSpot. HubSpot's company properties panel supports text, number, date, currency, and boolean types — field type in Kordeva determines the HubSpot property type selection.

Kordeva deals map to HubSpot deals. The deal name, amount, close date, and owner transfer directly. Kordeva deal stage names map to HubSpot pipeline stage names — if your Kordeva deals use a stage called 'Proposal Sent', it becomes a HubSpot stage label in the selected pipeline. Stage probability is assigned based on HubSpot's pipeline stage configuration.

Kordeva deal-level custom fields become HubSpot deal custom properties. HubSpot's deal properties panel has a separate section from company and contact properties — ensure your admin creates properties under the Deals object type. Property creation in HubSpot requires the property label, internal name (auto-generated), and type selection.

Kordeva stores an owner as a user reference on each record. The migration resolves Kordeva owner emails against HubSpot user emails. If a Kordeva owner has no matching HubSpot user, the record lands under a designated fallback owner and is flagged for manual reassignment. Kordeva owners without HubSpot access should be invited before migration day.

Kordeva engagement records with type 'call', 'email', 'meeting', or 'note' map to HubSpot's corresponding engagement objects. Original timestamps, engagement body content, and owner attribution are preserved. Each engagement is linked to its parent contact or company record using HubSpot's association API.

Kordeva allows a contact to be associated with multiple companies. HubSpot supports one primary company on the contact record plus additional associations via the Company Contact Associations feature. FlitStack migrates the most-recently-modified Kordeva association as the primary company and surfaces the rest as secondary associations in HubSpot.

Kordeva workflows do not have a HubSpot equivalent. Automation logic (triggers, conditions, actions) must be rebuilt in HubSpot using HubSpot's workflow builder or Operations Hub. FlitStack can export Kordeva workflow definitions as a rebuild reference document for your HubSpot admin.

Kordeva reports and dashboards do not transfer. The underlying data (deals, contacts, activities) migrates to HubSpot, where you can recreate reports using HubSpot's reporting tools. FlitStack confirms that the data supporting each Kordeva report is present in HubSpot so reporting can be rebuilt on the migrated dataset.