Migrate from KulaHub to monday CRM

KulaHub stores all entities as Contacts including organization records. We parse the contact name, email domain, and any company-name fields to split KulaHub Contacts into Monday.com People (individual records) and Companies (organization records). Organization-level fields from KulaHub (if any exist in custom fields) map to Monday.com Company columns. The relationship is created by linking each Person to its parent Company using the Monday.com Company integration. This split is designed during scoping and validated against a sample export before the production run.

KulaHub activity logs including telephone calls, emails, and system events attach to contact records as a chronological time-series. We export activities as date-ordered records and load them into Monday.com's Activity section on the corresponding People or Company item. Activity type (call, email, meeting) maps to Monday.com's activity type field, with notes and timestamps preserved as-is. System events (record created, record updated) migrate as internal notes or are excluded based on customer preference during scoping.

KulaHub stores campaign records, templates, and tracking data (opens, clicks, unsubscribes). Monday.com CRM does not have a native email campaign management module; email activities attach to People items but campaign-level reporting does not transfer intact. We export the campaign history including GDPR unsubscribe states as a linked table and present it to the customer for manual reference or rebuild in a dedicated email marketing tool post-migration. GDPR unsubscribe flags are written to a custom field on each affected Person record.

KulaHub documents attached to contacts link via a foreign-key relationship. We extract each document blob and re-associate it with the corresponding Monday.com People or Company item as a file attachment. File names and original upload timestamps are preserved. Documents without a clear parent contact are held in a staging table and presented to the customer for manual mapping before production load.

KulaHub tasks are assigned to specific users and linked to contacts. We map tasks 1:1 to Monday.com Tasks attached to the corresponding People or Company item, preserving the task description, due date, and assignment. Owner mapping resolves by matching KulaHub user email against the Monday.com workspace member list. Tasks without a matching user are assigned to the migration owner for the customer admin to reassign post-migration.

KulaHub users appear in activity logs and task assignments. We export the full user list first and map each KulaHub user to a Monday.com workspace member by email. Active and inactive status is preserved. Monday.com workspace seats are provisioned by the customer before migration; we validate seat count against user record count during discovery.

KulaHub captures website enquiries via forms linked to contacts, but the form-field schema is not publicly documented. We request a sample export of form-submission data during discovery to identify field names and data types. Each distinct form field becomes a custom column on the Monday.com People board, with the form submission source recorded as a column value. Fields without a Monday.com equivalent are held in a staging table for manual review.

KulaHub stores email unsubscribe states and GDPR preference flags per contact but the persistence format is undocumented. We export preference flags as custom fields on each Monday.com People record. Email opt-out states map to a Boolean custom field that the customer's admin configures as a filter in any email integration. This ensures existing suppression lists are respected by any connected marketing tool.