Migrate from KulaHub to HubSpot

KulaHub contacts migrate as HubSpot Contacts with all standard properties preserved. The HubSpot contact record gets its original create timestamp stored in a custom datetime property because HubSpot's native CreatedDate reflects the migration load time, not the source record creation date.

KulaHub companies map to HubSpot Companies, preserving fields such as name, domain, industry, and address. If KulaHub tracks a parent‑child company hierarchy, the top‑level company becomes the HubSpot parent, and subsidiaries attach as child companies. Contacts without a primary company are linked using HubSpot's secondary company association, ensuring no relationship is lost during migration. This structure maintains reporting continuity and supports CRM‑based territory analysis.

KulaHub deals map to HubSpot Deals. KulaHub's deal stage labels map to HubSpot Deal Pipeline stage values — if KulaHub uses a single pipeline, we create one HubSpot Deal Pipeline; if multiple deal lists exist, we create corresponding HubSpot pipelines. Stage-entry timestamps are preserved as HubSpot custom datetime properties.

KulaHub task records (calls, emails, notes logged against a contact) migrate as HubSpot engagements — a Call engagement, an Email engagement, or a Note engagement — preserving the original timestamp, owner, and the linked contact. KulaHub meeting records with a date/time range map to HubSpot Meeting engagements.

KulaHub owner records (sales reps assigned to contacts and deals) resolve by email match against HubSpot users. KulaHub owner IDs are stored as a custom property on migrated records for traceability. Any KulaHub owner without a matching HubSpot user is flagged before migration so your admin can create the HubSpot user or reassign records.

KulaHub custom fields created by the admin (beyond standard fields like firstname, email, phone) become HubSpot custom properties. If your HubSpot subscription is Starter or Professional, these properties are added to the existing Contact, Company, or Deal objects. Enterprise subscriptions allow standalone Custom Objects.

KulaHub file attachments on contacts or deals are downloaded and re-uploaded to HubSpot CRM Files, then linked back to the corresponding record. File size limits apply — HubSpot's file upload limit is 60MB per file for most account tiers. Inline images embedded in KulaHub notes are extracted and re-hosted in HubSpot's file manager.

If KulaHub tracks a buyer-stage or status field as a custom field on contacts, FlitStack AI maps those values to HubSpot's lifecycle_stage pick-list (subscriber, lead, MQL, SQL, customer, evangelist). Unmapped values are preserved as a custom text property for review before final assignment.

KulaHub allows a contact to be associated with one or more companies. HubSpot Contact records get a primary company association (the most-recently modified KulaHub link, or your specified rule) and additional companies stored in HubSpot's secondary company associations field. If the KulaHub association includes a role label (e.g., 'Decision Maker', 'Influencer'), that metadata is stored as a custom property on the HubSpot contact to preserve context for downstream segmentation.

KulaHub workflows and automation rules do not have a migration path to HubSpot. They must be rebuilt using HubSpot's Workflows tool (available in Operations Hub Professional and Enterprise). FlitStack AI exports your KulaHub workflow definitions as a structured JSON reference document your HubSpot admin can use during the rebuild.

KulaHub's saved reports and dashboard configurations do not transfer. The underlying data (contacts, companies, deals) migrates, but the report layouts, filters, and chart types are rebuilt in HubSpot's Analytics. FlitStack AI documents your KulaHub report field selections as a rebuild guide.

KulaHub API integrations (third‑party tools via webhook or REST API) cannot be migrated. They must be reconnected in HubSpot via native integrations, the HubSpot API, or middleware such as Zapier or Make. During migration, FlitStack AI documents your active integrations with endpoint URLs and auth details to guide the reconnection process.