Migrate from Kursaha to HubSpot

Kurosaha contacts map directly to HubSpot contacts. All standard properties (name, email, phone, job title, address) carry over as HubSpot native fields. Kurosaha contact properties that have no HubSpot equivalent migrate as custom properties — these are created in HubSpot before the migration run.

Kurosaha has no native lifecycle stage equivalent. We inspect Kurosaha contact properties for signals that indicate lifecycle position (e.g., campaign_enrolled, deal_associated, last_activity_date) and route records to appropriate HubSpot lifecycle stage values. We preserve the original signal data as custom properties so HubSpot admins can apply the correct lifecycle classification in HubSpot post-migration.

Kurosaha companies map to HubSpot companies. Name, domain, industry, employee count, and annual revenue migrate as HubSpot native fields. Kurosaha parent-child company relationships translate to HubSpot's company associations. Kurosaha's custom company properties carry over as HubSpot custom properties. We validate company domain uniqueness and flag duplicate company records for your HubSpot admin to resolve before the migration run.

Kurosaha deals map to HubSpot deals. Each deal's name, amount, close date, owner, and associated company migrate. Kurosaha deal status flags (e.g., open, won, lost) translate to HubSpot deal stage values via a status-to-stage value map built during the mapping phase. Kurosaha deal properties migrate as HubSpot custom properties.

Kurosaha does not have a visual pipeline construct — deals are flat records. We examine Kurosaha deal data to identify logical pipeline groupings (e.g., by deal type, product line, or account segment) and create corresponding named pipelines in HubSpot. Each pipeline's stages are defined in collaboration with your team during the pre-migration planning call.

Kurosaha campaigns store engagement events (email opens, link clicks, SMS sent, WhatsApp delivered) per contact. We map campaign membership to a HubSpot custom contact property indicating campaign enrollment, and each engagement event translates to a HubSpot engagement record with the channel, timestamp, and campaign reference preserved.

Multi-channel engagement events from Kurosaha migrate to HubSpot engagement records keyed by channel type. Email subscription opt-in and opt-out states translate to HubSpot's emailSubscription property. SMS and WhatsApp engagement events are stored as custom engagement properties in HubSpot since HubSpot's native engagement model focuses on email, calls, and meetings.

Kurosaha users with names and email addresses are resolved to HubSpot owners by email match. If a Kurosaha user has no corresponding HubSpot user, their records are assigned to a designated fallback owner, and the source owner email is preserved in a custom property for post-migration review.

Kurosaha campaign enrollment does not have a direct HubSpot equivalent. We preserve campaign membership as a multi-select custom contact property listing all campaigns a contact was enrolled in. HubSpot lists and active lists can be used to recreate campaign segments based on this property after migration.

Kurosaha files attached to contacts, companies, or deals are downloaded and re-uploaded to HubSpot Files, linked to the corresponding record. File size limits follow HubSpot's default upload limits. Files without an identifiable parent record are uploaded to a central HubSpot file folder and linked in a custom property on the contact.

Kurosaha custom contact properties are created as HubSpot custom contact properties before migration. We match property types (text, number, date, picklist) between platforms. Multi-select picklists in Kurosaha map to HubSpot multi-checkbox or multi-select property types. Properties with no matching type default to text and are flagged for HubSpot admin review.

Kurosaha custom deal properties map to HubSpot custom deal properties. We create each property in HubSpot during the schema setup phase and validate that deal-stage-specific properties are scoped correctly. Kurosaha deal properties tied to a specific deal type or product line may require separate HubSpot pipelines for clean stage segregation.