Migrate from Krayin CRM to HubSpot

Krayin's Person entity holds first name, last name, job title, phone, and email in a single record. FlitStack AI splits the full name into HubSpot's FirstName and LastName fields. The original name value is preserved in a custom Name_Original__c property for reference. Job title maps to Title, phone to Phone, and email to Email directly.

Krayin Leads map 1:1 to HubSpot Leads. The Krayin lead status value maps to HubSpot Lead Status pick-list; Krayin lead source maps to HubSpot leadsource. Krayin assignee user_id resolves to HubSpot owner by email match. Custom fields on Krayin Leads migrate as HubSpot custom properties created in the destination portal before the migration runs.

Krayin Companies map to HubSpot Companies with name, domain, industry, number of employees, and annual revenue carried over directly. Industry pick-list values that do not match HubSpot's default values are mapped value-by-value during the migration. Krayin's parent company relationship migrates as a Parent Company lookup in HubSpot.

Krayin Deals map to HubSpot Deals with deal name as dealname, amount, close date, and user owner. The Krayin pipeline maps to a HubSpot pipeline; each Krayin pipeline becomes one HubSpot pipeline. Stage names require value mapping since Krayin stage labels differ from HubSpot's default stage vocabulary. Krayin deal priority migrates as a custom Priority__c pick-list on HubSpot Deals.

Krayin Products split into two HubSpot objects: the catalog definition (name, SKU, price) becomes a HubSpot Product record, and the quantity-attached version on a deal becomes a HubSpot Line Item. The split is necessary because HubSpot treats Products and Line Items as separate entities with a many-to-one relationship between Line Item and Product.

Krayin Call activities migrate as HubSpot Tasks with Subject set to the call direction and outcome, Type set to Call, and the original timestamp and duration preserved as custom datetime and number fields. The Krayin user who logged the call resolves to a HubSpot owner by email. Parent record links to the associated Person or Lead are reconstructed using HubSpot's associations API.

Krayin Email activities migrate as HubSpot engagements on the Contact timeline. Subject, body, and direction (sent/received) map to HubSpot engagement properties. HubSpot's email engagement model stores the thread as a series of associations rather than a single record; each email in a thread is created as a separate engagement linked to the same Contact.

Krayin Meeting activities migrate as HubSpot Meetings with the original start and end timestamps, location, and organizer preserved. Attendees are reconstructed as Contact associations using the Krayin meeting invitee records. The meeting outcome and description map to HubSpot meeting properties; notes from Krayin become HubSpot meeting body.

Krayin Note activities migrate as HubSpot Notes attached to the parent record (Person, Lead, Company, or Deal). The Krayin note body maps to the HubSpot note body; timestamps and the Krayin user who created the note are preserved. Rich-text formatting in Krayin notes is downloaded and re-uploaded as attachments if the formatting does not carry over in plain-text transfer.

Krayin Tasks map to HubSpot Tasks with subject, description, due date, and completion status carried over directly. Krayin's task status values (pending, in progress, completed) map to HubSpot Task Status values. The Krayin assigned user resolves to a HubSpot owner by email. Tasks with no due date land in HubSpot without a due date rather than receiving a default.

Krayin Quotes migrate to HubSpot Quotes when the Quote object is available in the destination HubSpot tier. The quote number, line items, total amount, and validity dates map directly. If HubSpot Quotes are not available in the purchased tier, Krayin quotes are migrated as HubSpot Deals with line item attachments and quote metadata stored as custom fields.

Krayin Tags are label-based and can be applied to multiple entity types. HubSpot uses a property-based tagging model where each tag becomes a contact property. FlitStack AI creates a multi-checkbox or multi-select custom property in HubSpot and maps the Krayin tag list into that property so the tag associations are preserved on each Contact record.

Krayin custom objects built on Laravel packages map 1:1 to HubSpot Custom Objects. The migration creates the corresponding HubSpot CRM Object with the same display name and API name convention. N:N relationships between Krayin custom objects are mapped to HubSpot association schemas; your admin defines the association type labels in HubSpot's Object Relationships UI after migration.