How long does a Kylas Sales CRM to Nutshell migration take?

Most migrations land between two and four weeks for accounts under 10,000 records with clean pipelines and no custom objects. Migrations with extensive custom fields, multiple Kylas pipelines, or large engagement histories (over 100,000 activities) move to four to six weeks because of mapping complexity and reconciliation time. Nutshell's per-user plan at $13/user/month and the time required to rebuild Smart Lists and workflows are separate from migration duration.

Do Kylas workflow automations and Smart Lists migrate to Nutshell?

No. Kylas workflow automation rules are not exposed via the Kylas export API, so they cannot be transferred as code. We deliver a written inventory of every active Kylas workflow with its trigger, conditions, and actions for the customer's admin to rebuild in Nutshell. Nutshell's automation features are available on Growth and Enterprise tiers. Smart List filter criteria can be documented but the saved view definitions must be recreated manually in Nutshell. Teams should plan two to four hours per Smart List for manual rebuild.

What does a Kylas to Nutshell migration typically cost?

Migrations under 10,000 total records with no custom objects land between $3,000 and $5,000 and complete in two to three weeks. Migrations with custom fields, multiple pipelines, or engagement histories over 100,000 records move to $6,000-$8,000 and four to six weeks. Nutshell's subscription at $13/user/month is separate from the migration fee and is the customer's ongoing cost. Workflow rebuild and Smart List reconstruction are admin tasks, not migration line items.

Can we migrate our Kylas engagement history (calls, emails, meetings, tasks) to Nutshell?

Yes. Kylas Activity records attached to Leads, Contacts, Deals, and Companies migrate as Nutshell Activities with the parent record resolved at migration time. Call duration and disposition values transfer to Nutshell custom Activity fields. Activity timestamps are preserved to maintain the chronological timeline. Notes attached to records migrate as Nutshell Activity entries with the note content preserved.

What happens to Kylas reports and dashboards during migration?

Saved reports and dashboards in Kylas are configuration objects with query definitions that do not export via the standard data export path. We document the report logic (filters, groupings, metrics) so the customer's Nutshell admin can recreate reports manually. Reports should be treated as read-only historical reference rather than a migrated asset. Nutshell's reporting tools differ from Kylas, so report rebuilds require a translation step rather than a direct import.

What are Nutshell's custom field limits and how do they affect migration?

Nutshell's custom field allocation depends on the plan tier. We compare the Kylas custom field count against the customer's chosen Nutshell plan during scoping. If the destination tier supports fewer custom fields than the Kylas schema requires, we identify consolidation opportunities (merging related fields into multi-select picklists) and flag any that require a plan upgrade. Custom field types from Kylas are mapped to equivalent Nutshell field types during migration design.

Do we lose data if our Kylas account has more than one pipeline?

Nutshell supports a single pipeline per account on base and Growth tiers. If the Kylas account uses multiple named pipelines, we map each Kylas pipeline to a distinct set of Nutshell Deal stages and document the mapping. If a Kylas pipeline exceeds the stage count supported on the destination Nutshell tier, we consolidate adjacent stages and note the consolidation for customer approval before migration. All deal values, probabilities, and stage history transfer within the consolidated structure.

Who provisions Nutshell users before migration begins?

The customer's Nutshell admin provisions user accounts before production migration. We reconcile Kylas Owners by email against the provisioned Nutshell user list. Any Kylas Owner without a matching Nutshell User is held in a reconciliation queue for the admin to create or deactivate. Migration cannot complete with correct owner assignment until this step is resolved because OwnerId is a required reference on most standard objects in both platforms.

Kylas Sales CRM to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Moving from Kylas Sales CRM to Nutshell is a structural migration from a flat-rate Indian-origin CRM to a per-user US-focused CRM with unlimited contact storage. Kylas uses Leads, Deals, and Companies with dynamic Smart Lists and workflow automation; Nutshell uses People, Organizations, and Deals with saved views and no native automation builder on its base tier. We resolve the object-model differences (Kylas Lead vs Nutshell Lead, Kylas Company vs Nutshell Organization), transfer deal pipeline stages with probability percentages, and migrate activity history as Activity records linked to the correct parent record. Kylas Smart List definitions do not export as persistent record sets, and Kylas workflow automation rules are not accessible via API, so we document both for manual rebuild in Nutshell rather than transferring them as code.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Kylas Sales CRM

What's pushing teams away

Record storage caps on the free tier (1,000 records) force an early upgrade, and some reviewers on Capterra and Reddit report the $200/month flat rate feels expensive relative to bare-bones alternatives priced at $15/user.
The native integration marketplace covers 80+ apps but some advanced ERP and accounting connectors require third-party middleware, leading teams on complex tech stacks to feel limited.
Custom workflow automations built inside Kylas do not export as reusable templates, meaning teams migrating away must manually rebuild every automation from scratch—a cost that catches some churners off guard.
Exporting Smart Lists and filtered views requires navigating the Data Management section in the UI; there is no single bulk-API call to dump all filtered record sets, making programmatic large-scale exports more involved than expected.

Choosing

Nutshell

What's pulling them in

Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Kylas Sales CRM objects map to Nutshell

Each row shows how a Kylas Sales CRM object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Kylas Sales CRM

Lead

maps to

Nutshell

Lead

1:1

Fully supported

Kylas Lead records (with lead_score, lead_source, and status fields) map directly to Nutshell Leads. We preserve the lead score as a numeric custom field on the Nutshell Lead, and the original lead_source value maps to the standard Nutshell source field. Inactive Leads from Kylas map to Nutshell Leads with a closed status rather than being omitted from migration.

Kylas Sales CRM

Contact

maps to

Nutshell

Person

1:1

Fully supported

Kylas Contacts with email addresses map to Nutshell People. The email address is used as the dedupe key during import. Custom properties on Kylas Contacts are created as custom fields in Nutshell and remapped, with picklist value IDs translated to Nutshell picklist values. Lifecycle stage metadata from Kylas is preserved as a custom text field on the Nutshell Person for audit continuity.

Kylas Sales CRM

Company

maps to

Nutshell

Organization

1:1

Fully supported

Kylas Company records map to Nutshell Organization. The company domain becomes the Organization website field and is used as a secondary dedupe key alongside the primary Organization name. Industry classification and company size migrate to Nutshell custom fields if they do not map to standard Organization fields.

Kylas Sales CRM

Deal

maps to

Nutshell

Deal

1:1

Fully supported

Kylas Deals map to Nutshell Deals with the deal value, expected close date, owner assignment, and weighted probability preserved. Pipeline stage names from Kylas map to Nutshell stage names, and stage probability percentages transfer to Nutshell's stage probability settings. Closed-won and closed-lost reasons from Kylas custom fields migrate to Nutshell custom deal fields.

Kylas Sales CRM

Pipeline Stage

maps to

Nutshell

Deal Stage

lossy

Fully supported

Kylas pipeline stages map to Nutshell Deal stages with probability percentages preserved. If a Kylas pipeline has more stages than the destination Nutshell plan supports, we collapse adjacent stages and document the consolidation decision for the customer's approval before migration begins.

Kylas Sales CRM

Activity (Task, Call, Note)

maps to

Nutshell

Activity

1:1

Fully supported

Kylas Activity records (tasks, calls, notes attached to Leads, Contacts, Deals, and Companies) migrate as Nutshell Activities with the parent record resolved at migration time. Call duration and disposition from Kylas migrate to custom Nutshell Activity fields. Activity timestamps are preserved to maintain the historical timeline against the correct Person, Organization, or Deal.

Kylas Sales CRM

Document

maps to

Nutshell

Attachment

1:1

Fully supported

Documents stored in Kylas are exported as binary blobs and mapped to Nutshell's attachment model, preserving the parent record association (Lead, Person, Organization, or Deal). Large document stores may require chunked transfer and are validated for file size compatibility with Nutshell's attachment limits on the destination tier.

Kylas Sales CRM

Tag

maps to

Nutshell

Tag

1:1

Fully supported

Kylas tags apply across objects. We export the full tag vocabulary and apply each tag to the corresponding Nutshell record during migration, merging duplicate tag names that result from cross-object tagging in Kylas.

Kylas Sales CRM

User (Owner)

maps to

Nutshell

User

1:1

Fully supported

Kylas user records (name, email, role) are exported and matched by email against Nutshell Users. We flag inactive Kylas users for the customer's Nutshell admin to activate or archive. Owner assignment on Leads, Contacts, Deals, and Activities resolves via the email match to the Nutshell User ID at migration time.

Kylas Sales CRM	Nutshell	Compatibility
Lead	Lead1:1	Fully supported
Contact	Person1:1	Fully supported
Company	Organization1:1	Fully supported
Deal	Deal1:1	Fully supported
Pipeline Stage	Deal Stagelossy	Fully supported
Activity (Task, Call, Note)	Activity1:1	Fully supported
Document	Attachment1:1	Fully supported
Tag	Tag1:1	Fully supported
User (Owner)	User1:1	Fully supported

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Kylas Sales CRM gotchas

High

Record storage caps gate migration scope

Medium

Smart List filter criteria are non-exportable

High

Workflow automation rules cannot be transferred

Low

API lacks publicly documented rate limits

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Kylas Sales CRM gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
High	Record storage caps gate migration scope	High	Contact tier limits enforced on import
Medium	Smart List filter criteria are non-exportable	Medium	No bulk API endpoint requires paginated extraction
High	Workflow automation rules cannot be transferred	Medium	Email sequences not exportable via API
Low	API lacks publicly documented rate limits	Medium	Foundation plan disables key sales features

Pair-specific challenges

Smart List definitions are non-exportable from Kylas

Kylas Smart Lists are dynamic saved searches evaluated at display time. They have no persistent member list to dump, and the filter criteria are not exposed via the export API. We export the filter logic for each Smart List so customers can document the criteria, but the definition itself must be recreated manually in Nutshell as a saved view. Teams that rely heavily on Smart Lists for segment-based reporting should plan for two to four hours of admin time per Smart List to rebuild in Nutshell.
Kylas workflow automation rules cannot be transferred

Kylas workflow automation configuration (triggers, conditions, action sequences) is not exposed through the export API. Any automation the customer has built—assignment rules, stage-change triggers, email autoresponders—must be documented by us as a configuration inventory and rebuilt manually in Nutshell. Nutshell's automation features (available on Growth and Enterprise tiers) use a different model, so the rebuild requires re-design rather than a literal translation. This is a platform-level restriction, not a limitation of our migration tooling.
Kylas API lacks publicly documented rate limits

Kylas publishes a REST API for integrations, but we found no publicly documented rate-limit ceiling. During migration we throttle API calls conservatively and monitor for 429 responses, backing off exponentially. Customers with real-time integrations feeding into Kylas should validate their own integration behavior under load before assuming uninterrupted write access during the migration window.
Nutshell custom field limits vary by plan tier

Nutshell's custom field allocation depends on the destination plan tier. We audit the customer's chosen Nutshell plan during scoping and compare it against the Kylas custom field count. If the destination tier has fewer available custom fields than the Kylas schema requires, we flag which fields can be consolidated (multi-select picklists for related single-select fields) and which require a plan upgrade.

Migration approach

Six steps for a successful Kylas Sales CRM to Nutshell data migration

Discovery and destination plan selection

We audit the source Kylas account across plan tier, record counts per object, custom field inventory, pipeline count and stage definitions, active workflow count, and engagement volume. We pair this with the customer's chosen Nutshell plan to identify any tier constraints (custom field limits, automation availability) that affect migration scope. The discovery output is a written migration scope document with object counts, custom field mapping, and any plan-tier gaps requiring resolution before migration begins.
Schema design and pipeline stage mapping

We design the destination schema in Nutshell, creating custom fields to match Kylas field types (text, number, date, picklist, multi-select). Picklist value IDs from Kylas are translated to Nutshell picklist values during this phase. Pipeline stage names and probability percentages from Kylas are configured as Nutshell Deal stages. We document the Smart List filter criteria separately for manual recreation and prepare a written inventory of all Kylas workflow rules for the automation rebuild phase.
Sandbox migration and reconciliation

We run a full migration into a Nutshell sandbox or trial account using production-like data volume. The customer's admin reconciles record counts (Leads in, People in, Organizations in, Deals in, Activities in), spot-checks 20-30 records against the Kylas source, and validates that pipeline stages, owner assignments, and custom field values match. Any mapping corrections happen here, not in production. Smart List filter criteria are reviewed for accuracy at this stage.
Owner reconciliation and user provisioning

We extract every distinct Kylas Owner referenced on Lead, Contact, Deal, and Activity records and match by email against the destination Nutshell account's user list. Owners without a matching Nutshell User are placed in a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignment on migrating records resolves via email match at this step.
Production migration in dependency order

We run production migration in record-dependency order: Users (validated), Organizations (from Kylas Companies), People (with Organization resolved), Leads (with Owner resolved), Deals (with Person, Organization, and Owner resolved), Activities (with parent record resolved), Documents (attached to parent records), and Tags (applied across all records). Each phase emits a row-count reconciliation report before the next phase begins. We use conservative throttling and exponential backoff to stay within Kylas API behavior limits.
Cutover, validation, and workflow rebuild handoff

We freeze Kylas writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the Smart List filter criteria document and the workflow automation inventory to the customer's admin team. We support a one-week hypercare window for reconciliation issues. We do not rebuild Kylas workflows or Smart Lists inside the migration scope; those are separate admin tasks or engagements.

Platform deep dives

Context on both ends of the pair

Kylas Sales CRM

Source

Strengths

Unlimited-user flat-rate pricing simplifies budgeting for growing sales teams without per-seat inflation.
Mobile-first design with native iOS and Android apps keeps field reps productive without desktop access.
Built-in WhatsApp, SMS, and calling integration reduces reliance on third-party telephony tools.
Drag-and-drop pipeline configuration lets sales managers adjust deal stages without developer involvement.
Lead scoring and automated routing provide tiered prioritisation without requiring a data analyst on staff.

Weaknesses

Free tier caps at 1,000 records, pushing teams to upgrade sooner than comparable CRMs with higher free limits.
Workflow automation cannot be exported, requiring manual rebuild when switching platforms—a significant change-management cost.
Smart Lists are query-based and not exportable as static record sets, limiting migration completeness for teams relying heavily on filtered views.
The API is not publicly documented with rate limits or bulk endpoints, making programmatic migration planning less predictable.
The platform is primarily marketed to Indian and Southeast Asian SMBs; enterprise teams with global compliance requirements may find regional data-residency options limited.

Nutshell

Destination

Strengths

Simple, intuitive interface with minimal learning curve for sales teams new to CRM
Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
Full data export tool available for all account data including backups
Open JSON-RPC API allows programmatic access to all core objects
Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

	Kylas Sales CRM Source	Nutshell Destination
Strengths	Unlimited-user flat-rate pricing simplifies budgeting for growing sales teams without per-seat inflation. Mobile-first design with native iOS and Android apps keeps field reps productive without desktop access. Built-in WhatsApp, SMS, and calling integration reduces reliance on third-party telephony tools. Drag-and-drop pipeline configuration lets sales managers adjust deal stages without developer involvement. Lead scoring and automated routing provide tiered prioritisation without requiring a data analyst on staff.	Simple, intuitive interface with minimal learning curve for sales teams new to CRM Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost Full data export tool available for all account data including backups Open JSON-RPC API allows programmatic access to all core objects Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication
Weaknesses	Free tier caps at 1,000 records, pushing teams to upgrade sooner than comparable CRMs with higher free limits. Workflow automation cannot be exported, requiring manual rebuild when switching platforms—a significant change-management cost. Smart Lists are query-based and not exportable as static record sets, limiting migration completeness for teams relying heavily on filtered views. The API is not publicly documented with rate limits or bulk endpoints, making programmatic migration planning less predictable. The platform is primarily marketed to Indian and Southeast Asian SMBs; enterprise teams with global compliance requirements may find regional data-residency options limited.	Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Kylas Sales CRM and Nutshell.

Object compatibility
B
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
C
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
B
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
B
Kylas Sales CRM: Not publicly documented.
Data volume sensitivity
B
Kylas Sales CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

POPULAR PLATFORMS

POPULAR MIGRATIONS

Migrate from Kylas Sales CRM to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Kylas Sales CRM

Nutshell

How Kylas Sales CRM objects map to Nutshell

What specifically takes care here

Six steps for a successful Kylas Sales CRM to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Kylas Sales CRM to Nutshell migration cost

What are you migrating?

Frequently asked questions about Kylas Sales CRM to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from Kylas Sales CRM.
Land in Nutshell, intact.

Migrate from Kylas Sales CRM to Nutshell

What this migration involves

Field-level fidelity

Schema-aware mapping

Relationships preserved

Full activity history

Attachments & notes

Two sides of the same decision

Kylas Sales CRM

Nutshell

How Kylas Sales CRM objects map to Nutshell

What specifically takes care here

Six steps for a successful Kylas Sales CRM to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Kylas Sales CRM to Nutshell migration cost

Frequently asked questions about Kylas Sales CRM to Nutshell data migrations

Can't find your answer?

How long does a Kylas Sales CRM to Nutshell migration take?

Do Kylas workflow automations and Smart Lists migrate to Nutshell?

What does a Kylas to Nutshell migration typically cost?

Can we migrate our Kylas engagement history (calls, emails, meetings, tasks) to Nutshell?

What happens to Kylas reports and dashboards during migration?

What are Nutshell's custom field limits and how do they affect migration?

Do we lose data if our Kylas account has more than one pipeline?

Who provisions Nutshell users before migration begins?

Related migrations to explore

Move from Kylas Sales CRM. Land in Nutshell, intact.

Move from Kylas Sales CRM.
Land in Nutshell, intact.