Migrate from Kinabase to Freshsales

Kinabase Collections that hold individual people (Contacts, Customers, People) map to Freshsales Contact. The Collection's Fields map to Freshsales standard fields (first_name, last_name, email, phone, address) with any additional Fields created as Freshsales custom fields. Email uniqueness is enforced in Freshsales; we deduplicate by email before import and flag duplicate records for customer resolution.

Kinabase Collections holding companies or organisations map to Freshsales Account. The Account Name becomes the primary key field. Website, industry, and address Fields map to Freshsales standard fields. We create the Account before importing any related Contacts so that AccountId lookups are satisfied at import time.

Kinabase Collections representing transactional or project records map to Freshsales Deal. The deal name, amount, and stage map to Freshsales Deal fields. Stage values from Kinabase custom Fields map to Freshsales Deal stage dropdown. If the Collection has a monetary Field, we map it to Freshsales Deal amount fields.

Kinabase Collections that have no direct Freshsales standard object equivalent (Projects, Subscriptions, Properties, Vehicles, Cases) map to Freshsales custom objects on Growth and above tiers. We pre-create the Freshsales custom object schema, including all custom Fields and any lookup relationships to Contacts, Accounts, or Deals, before data import begins.

Kinabase linked collection Fields create cross-record references across Collections. In Freshsales, these map to lookup Fields on custom objects if the Freshsales edition supports custom object relationships. For standard objects or lower tiers, we denormalise the referenced record's ID or name as a text field and flag this for the customer's admin to validate relationship semantics post-migration.

Kinabase Activities attached to Records map to Freshsales Tasks, Calls, and Meetings based on activity type. Call duration and disposition map to Freshsales Call custom fields. Meeting details (subject, start time, end time) map to Freshsales Meeting. We preserve activity timestamps and owner assignments by resolving Kinabase Owner references against Freshsales Users.

Kinabase standalone Tasks map to Freshsales Task with Status, Priority, due_date, and assigned owner preserved. Tasks linked to specific Records carry the parent record's lookup reference (Contact, Account, or Deal) in the WhatId field. Open and completed status maps directly to Freshsales task status values.

Kinabase Computed Fields derive their value from a formula expression. Since Freshsales does not support computed Field formulas, we evaluate the formula expression at migration time and write the resulting value as a static custom field. The formula logic is not preserved; only the computed result transfers. We flag every computed Field in the pre-migration audit for customer review.

Kinabase document attachments store a reference URL or filename. We export the reference metadata and map it to Freshsales as a text URL field on the parent record or as a note with a link. Actual file content transfer depends on whether the destination Freshsales plan supports file attachments and whether the source file host allows cross-platform access.

Kinabase stage and status values (Draft, Active, Approved, Closed) stored as Fields on Collections map to Freshsales picklist or dropdown Fields on the target object. We create the picklist values in Freshsales before migration so that imported records do not fail on a restricted picklist validation error.