Kylas to HubSpot
Cloud sales CRM for SMB and mid-market teams, mainly in India. It covers leads, contacts, companies, deals, pipelines, quotations, workflows and reporting.
Kylas data can move into HubSpot, landing mainly in Sales Hub. 4 of 10 mapped objects move directly (Contacts, Companies, Deals and Products & Services); 4 items need manual work and 3 do not move. Plan roughly 2-4 weeks for a small move and 8-14 weeks for a large one.
Migration checklist for Kylas
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<10k records
CSV import with simple pipeline.
Mid migration
10k-100k records
Includes activities, workflows and integrations.
Large migration
>100k records
Likely needs API extraction and extensive automation rebuild.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Kylas: what you need to get in, what lands in HubSpot, and what will not.
REST (Postman-documented collection) plus webhooks
API key from Settings > Integrations > API Keys
Tenant-admin to generate the API key. Bulk export needs Create permission on Data export plus Read on the entities.
Choose your route
How will you move the data?
No native connector was found.
- You need: API key from Settings > Integrations > API Keys
- Permission: Tenant-admin to generate the API key. Bulk export needs Create permission on Data export plus Read on the entities.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Settings > Data Management > Export: CSV per entity (Leads, Contacts, Deals, Companies, Quotations, Calls, Meetings, Tasks, Products & Services)
- Smart List exports
- Export can include associated Notes and Meetings
- Field sales location history export
- API key plus webhooks for programmatic extraction
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 8-14 weeks, usually phased.
Talk to a partnerWhere each object lands
In Kylas
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Contacts | Contacts | yes | CSV export, then HubSpot import. |
| Companies | Companies | yes | CSV export; association to contacts must be rebuilt using the exported IDs or names. |
| Leads | Contacts | partial | Leads have no HubSpot equivalent; map them to Contacts with lead status, or to Deals. Kylas leads convert into contacts, deals or companies. |
| Deals | Deals | yes | Pipeline and stage IDs must be mapped to HubSpot pipelines. Kylas allows multiple contacts per deal. |
| Calls, Meetings, Tasks | Calls, Meetings, Tasks | partial | Exported as CSV; the HubSpot import needs object associations in the file. |
| Notes | Notes | partial | Exportable together with the parent entity. |
| Products & Services | Products | yes | CSV export. |
| Quotations | Quotes | manual | Exportable to CSV, but HubSpot quotes need templates and line items rebuilt. |
| Owners/users | Contacts, Companies, Deals | partial | Owner is a field in the exports; users must exist in HubSpot first. |
| Pipelines and stages | Deals | manual | Rebuild in HubSpot; Kylas pipeline and stage IDs are viewable in settings. |
What to expect
Configuration, not exportable data; rebuild as HubSpot workflows.
Not in the data export; recreate in HubSpot permission sets and teams.
No documented export of report definitions.
Automation is Kylas-specific.
Picklist value IDs are Kylas-specific.
These feed Kylas via API key.
Report definitions are not exported.
Audit association coverage in a sample export. Use the API for relationship data if the CSV lacks it.
Confirm plan and export permission before the project starts.
Confirm limits with Kylas before any API-based extraction.
Decide on a lead-to-contact or deal rule up front.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Export path (CSV) and API key/Postman API collection are documented by Kylas. Object-level field mapping, rate limits, residency and certifications were not verified. HubSpot-side mapping rests on category-level knowledge. One third-party site claims there is no API, which conflicts with Kylas's own docs.
Sources
Related migrations
Frequently asked questions
How do I migrate Kylas to HubSpot?
1. Confirm the plan and that an admin has Export permission on all entities. 2. Generate the API key under Integrations > API Keys. 3. Inventory entities, custom fields, pipelines and stages, and note the picklist IDs. 4. Decide how Kylas Leads map to HubSpot Contacts, Deals or lifecycle stage.
What data can move from Kylas to HubSpot?
These objects move directly: Contacts, Companies, Deals and Products & Services. Check the mapping table for partial and manual items.
What does not move from Kylas to HubSpot?
Workflow automations, lead routing rules and assignment rules, Roles, permissions and team hierarchies and Reports and dashboards. Plan to rebuild or retire these.
How long does a Kylas to HubSpot migration take?
Small (<10k records): 2-4 weeks. Mid (10k-100k records): 4-8 weeks. Large (>100k records): 8-14 weeks. These are planning estimates, not a quote.
What access do I need to export from Kylas?
API key from Settings > Integrations > API Keys Tenant-admin to generate the API key. Bulk export needs Create permission on Data export plus Read on the entities.
What compliance issues apply when moving Kylas data?
Check: Employee location tracking data (field sales) and Possible India DPDP-regulated personal data. Agree consent, retention and access rules before exporting.
Moving Kylas into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner