How long does a Flowlu to Nutshell migration take?

Most migrations land between one and three weeks for accounts under 10,000 Contacts and 2,000 Deals with a straightforward custom field schema. Migrations with multiple Flowlu pipelines, large custom field sets, or customer requirements to document project and invoice data for manual extraction move to four to six weeks. The primary timeline variable is the reconciliation work for Owner provisioning and custom field mapping review before import begins.

What happens to my Flowlu projects, tasks, and invoices?

Nutshell is a CRM-only platform with no native project management, invoicing, or knowledge base modules. We do not migrate Projects, Tasks, Invoices, Time Entries, or Knowledge Base articles into Nutshell. Instead, we extract this data as structured CSV exports during migration scoping and deliver it alongside the Nutshell migration report. Your admin uses the CSV to import into a project management tool or document management system of choice. Deal-to-Project references from Flowlu are preserved as text fields on the migrated Deals.

Do Flowlu Workflows migrate to Nutshell?

No. Flowlu automations and integrations do not carry over after import per Flowlu's own migration documentation. Workflows built in Flowlu's automation builder must be rebuilt in Nutshell or another tool post-migration. We deliver a written inventory of every active Flowlu automation with its trigger, conditions, and actions so that your admin can evaluate what to rebuild in Nutshell's CRM workflow rules or an alternative automation platform. This is a known gap that most teams underestimate until after import.

What does a Flowlu to Nutshell migration typically cost?

Migrations under 10,000 Contacts, 2,000 Deals, and a straightforward custom field schema land between $2,500 and $3,500. Migrations with multiple pipelines, large custom field schemas, or customer requirements to document project and invoice data for manual extraction move to $4,500-$6,500. Nutshell subscription costs ($19-$39 per user per month on annual billing) sit outside the migration fee. Flowlu's September 2025 pricing shift to per-seat billing means many teams find Nutshell's unlimited-contact model cost-predictable at comparable per-seat rates.

What happens to my Flowlu custom fields?

Flowlu Custom Fields on Contacts, Companies, and Opportunities migrate to Nutshell custom fields on the equivalent objects. We extract the complete custom field schema per object during scoping, map each to a Nutshell field type, and flag mismatches for manual review before import. Custom fields on non-CRM objects (Projects, Tasks, Invoices) are included in the CSV export deliverable rather than a direct migration. Mismatched field types (e.g., Flowlu list fields with multiple selections vs. Nutshell text fields) are flagged for customer decision during scoping.

Can we keep Nutshell as our CRM and use another tool for projects?

Yes. This is one of the most common migration patterns for teams leaving Flowlu. Nutshell handles the CRM layer (Contacts, Companies, Deals, pipeline management) while a dedicated project management tool (Asana, Monday.com, ClickUp, or another platform) handles Projects and Tasks. We can migrate your CRM data to Nutshell and your Project and Task data to your chosen PM tool in a coordinated migration, with the project-export deliverable from Flowlu used as the source for the PM tool import.

Does Nutshell offer migration assistance included with subscription?

Nutshell's marketing materials reference data migration assistance as an included benefit on paid subscriptions. However, Nutshell's built-in migration tools focus on standard CRM data (Contacts, Companies, Deals) and may not handle Flowlu-specific custom fields, multi-pipeline structures, or the cross-object relationship resolution that a full CRM migration requires. We supplement Nutshell's built-in assistance with field-level mapping, pipeline configuration, custom field migration, and Owner reconciliation that the standard tools do not cover.

Flowlu to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

Moving from Flowlu to Nutshell is a scope-refinement migration: Nutshell is a purpose-built CRM, while Flowlu bundles CRM, project management, invoicing, and knowledge base into a single platform. We migrate the CRM layer (Contacts, Companies, Deals, and Custom Fields) with full relationship preservation between records. Projects, Tasks, Invoices, Time Entries, and Knowledge Base articles do not have native equivalents in Nutshell and are flagged during scoping for manual export or alternative handling. Flowlu's automations do not carry over after import per Flowlu's own migration documentation, and we deliver a written rebuild checklist for your admin. Nutshell's per-user pricing and unlimited contact model replace Flowlu's tiered contact limits, which caught long-term users off guard after the September 2025 pricing shift to per-seat billing.

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

Flowlu

What's pushing teams away

The September 2025 shift from flat-rate to per-seat pricing caught long-term users off guard, with reviewers noting the cost increase made Flowlu less competitive for larger teams.
Steep learning curve and complex interface slow adoption for new team members, with multiple G2 reviewers describing the onboarding as overwhelming compared to simpler tools like ClickUp or Asana.
Absence of a native Mac desktop app and no dark mode frustrate users who work primarily on macOS or prefer low-light interfaces, per G2 and Capterra reviews.
The Free plan caps contacts at 100 and locks email sync behind paid tiers, leading users to feel the free tier functions as a trial rather than a viable long-term option.
Missing native e-signature and contract capabilities force teams to use third-party tools like DocuSign, creating data silos that contradict Flowlu's all-in-one positioning.

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 Flowlu objects map to Nutshell

Each row shows how a Flowlu 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.

Flowlu

Contact

maps to

Nutshell

Contact

1:1

Fully supported

Flowlu Contacts map to Nutshell Contacts. We map name fields (first_name, last_name), email, phone, company association (via the Contact-Company link), lifecycle stage, and any custom field values. Deduplication uses email as the primary key. Flowlu's lifecycle stage property maps to Nutshell's Status or a custom field for audit trail. The Contact-Company relationship is resolved by matching Flowlu's company_id to the pre-imported Nutshell Company record.

Flowlu

Company

maps to

Nutshell

Company

1:1

Fully supported

Flowlu Companies map to Nutshell Companies. We map company name, industry, website, address fields, and custom fields. Companies are imported before Contacts so that the company reference on each Contact is satisfied at the moment of import. Nutshell does not have a separate Account concept; Company is the single organizational record type.

Flowlu

Opportunity

maps to

Nutshell

Deal

1:1

Fully supported

Flowlu Opportunities map to Nutshell Deals. We map deal name, stage, amount, probability, expected close date, and custom fields. The pipeline and stage assignment from Flowlu determines the Nutshell pipeline and stage the deal lands in. Nutshell's Deal object has a direct probability field; we map Flowlu's probability percentage directly or compute from the stage mapping table.

Flowlu

Pipeline

maps to

Nutshell

Pipeline

1:1

Fully supported

Flowlu Pipelines map to Nutshell Pipelines. We map pipeline name and stage definitions (stage name, order, and probability). Active deals are placed in their current pipeline and stage at migration time. Nutshell Pipelines are created before Deal import so that each Deal has a valid pipeline reference on insert.

Flowlu

Pipeline Stage

maps to

Nutshell

Stage

lossy

Fully supported

Individual stages within each Flowlu Pipeline map to Nutshell Stage values scoped to that Pipeline. Stage display order and probability percentages migrate directly. Nutshell stages are scoped per Pipeline, matching Flowlu's architecture.

Flowlu

Custom Fields (CRM objects)

maps to

Nutshell

Custom Fields

lossy

Fully supported

Flowlu Custom Fields on Contacts, Companies, and Opportunities map to Nutshell custom fields on the equivalent objects. Each field is mapped by type: Flowlu text fields map to Nutshell text fields, list fields map to drop-down or multi-select depending on Nutshell's field support, date fields map to date fields. We extract the complete custom field schema per object type during scoping and map each before import. Mismatched field types are flagged for manual review.

Flowlu

User

maps to

Nutshell

User

1:1

Fully supported

Flowlu Users map to Nutshell Users by email match. We extract the user roster and match against the destination Nutshell account's user list. Active Flowlu users must have a corresponding Nutshell user provisioned before Deal and Contact import begins because Owner fields are required on standard imports.

Flowlu

Projects

maps to

Nutshell

Not supported

lossy

Fully supported

Flowlu Projects have no native equivalent in Nutshell. Nutshell is a CRM platform without project management capability. We extract project data (name, description, deadline, status, custom fields) during scoping and deliver a structured CSV export for the customer's admin to handle separately. Project assignments on migrated Deals (e.g., deal linked to a project reference) are preserved as a text field on the Deal rather than a relationship.

Flowlu	Nutshell	Compatibility
Contact	Contact1:1	Fully supported
Company	Company1:1	Fully supported
Opportunity	Deal1:1	Fully supported
Pipeline	Pipeline1:1	Fully supported
Pipeline Stage	Stagelossy	Fully supported
Custom Fields (CRM objects)	Custom Fieldslossy	Fully supported
User	User1:1	Fully supported
Projects	Not supportedlossy	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.

Flowlu gotchas

High

Free tier contact cap is a hard migration target

High

Automations and integrations must be rebuilt after migration

Medium

No refunds on paid subscriptions after billing period starts

Medium

Custom Fields on multiple object types require field-level mapping

Low

API rate limits are not publicly documented

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

Flowlu gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
High	Free tier contact cap is a hard migration target	High	Contact tier limits enforced on import
High	Automations and integrations must be rebuilt after migration	Medium	No bulk API endpoint requires paginated extraction
Medium	No refunds on paid subscriptions after billing period starts	Medium	Email sequences not exportable via API
Medium	Custom Fields on multiple object types require field-level mapping	Medium	Foundation plan disables key sales features
Low	API rate limits are not publicly documented

Pair-specific challenges

Projects, Tasks, Invoices, and Knowledge Base have no Nutshell home

Flowlu bundles CRM with Projects, Tasks, Invoices, Time Entries, and Knowledge Base. Nutshell is a CRM-only platform with no project management, invoicing, or knowledge base modules. We migrate the CRM layer (Contacts, Companies, Deals, Custom Fields) fully. Project data, task data, invoice records, and knowledge base articles are extracted as structured CSV exports and delivered to the customer for manual handling in their chosen tool. Deal-to-Project references are preserved as text fields on the Deal rather than a relationship. This scope gap must be understood before migration begins.
Flowlu automations and integrations do not migrate

Flowlu's own migration documentation explicitly states that automations, integrations, and API connections do not carry over after import. Workflow rules, triggers, and webhook configurations from Flowlu's automation builder must be rebuilt in Nutshell or another tool post-migration. We extract a written inventory of every active Flowlu automation during scoping and deliver it as a rebuild checklist. Nutshell's own workflow rules operate within the CRM module only and have a different trigger-and-action model from Flowlu's cross-module builder.
Flowlu Free plan contact cap is a hard migration ceiling

Flowlu's Free plan limits CRM to 100 contacts and one pipeline. Teams that outgrew the Free plan under a paid plan have their full record set available for migration. We check the source account's plan tier during scoping and alert the customer to any contact volume that would exceed a Nutshell trial or cause import truncation. Nutshell's unlimited contact model accommodates any Flowlu contact volume, but the customer must provision a paid Nutshell plan before import begins.
Flowlu custom fields on multiple object types require field-level mapping

Flowlu allows Custom Fields on Projects, Tasks, Opportunities, Contacts, Companies, Knowledge Base items, and more, with different field sets per object type. We extract the complete custom field schema per object during scoping, map each to the equivalent Nutshell field type, and flag mismatches (e.g., Flowlu list fields vs. Nutshell text fields) for manual review. Custom fields on non-CRM objects (Projects, Tasks, Invoices) are included in the CSV export deliverable rather than a direct migration.
Flowlu API rate limits are not publicly documented

Flowlu does not publish API rate limit thresholds in its public documentation. When extracting data via the Flowlu API, we implement exponential backoff and error handling for 429 responses. We monitor for rate limit hits during extraction and slow the request cadence accordingly. For large data volumes this can extend extraction timelines unpredictably. CSV export is used as a fallback or supplementary extraction method where the API encounters sustained throttling.

Migration approach

Six steps for a successful Flowlu to Nutshell data migration

Discovery and scoping

We audit the source Flowlu account across plan tier, object inventory (Contacts, Companies, Opportunities, Pipelines, Custom Fields, Projects, Invoices), active workflow count, and user roster. We identify which records fall within the CRM migration scope and which fall into the project/invoice export deliverable scope. We also verify the destination Nutshell account plan and user count. The discovery output is a written migration scope that explicitly separates what migrates directly into Nutshell from what extracts as CSV.
Custom field schema extraction and mapping

We extract the complete custom field schema per object type from Flowlu: field name, field type (text, number, date, list, checkbox, etc.), required status, and which object each field attaches to. We map each to a Nutshell equivalent custom field. Fields without a direct Nutshell type (e.g., Flowlu Agile-specific fields) are flagged for manual assignment. The mapping document is reviewed by the customer before any import begins.
Nutshell pipeline and stage configuration

We configure Nutshell Pipelines and Stages to match the Flowlu source before any record import. This includes creating one Nutshell Pipeline per Flowlu Pipeline, setting stage names and display order, and mapping probability percentages. Pipeline configuration is validated in the Nutshell sandbox or test environment before production migration begins.
Owner and user reconciliation

We extract every distinct Flowlu Owner referenced on Contact, Company, and Deal records and match by email against the destination Nutshell account's user list. Owners without a matching Nutshell user go to a reconciliation queue for the customer's admin to provision before import. User provisioning must complete before record import because Owner fields are required on standard imports.
CRM record migration in dependency order

We run production migration in record-dependency order: Companies first (as the organization record), then Contacts (with company reference resolved), then Pipelines and Stages, then Deals (with owner, company, and pipeline reference resolved). Custom Fields are created via Nutshell's custom field API before record import begins. Each phase emits a row-count reconciliation report before the next phase starts. Projects, Tasks, Invoices, and Knowledge Base articles are exported as structured CSV and delivered alongside the Nutshell migration report.
Cutover, validation, and automation rebuild handoff

We freeze Flowlu 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 automation rebuild checklist (extracted from Flowlu's workflow inventory) and the project/invoice CSV export to the customer's admin team. We support a one-week hypercare window to resolve any reconciliation issues. We do not rebuild Flowlu automations as Nutshell workflow rules inside the migration scope; that is a separate engagement or an internal admin task.

Platform deep dives

Context on both ends of the pair

Flowlu

Source

Strengths

Combines CRM, project management, invoicing, and knowledge base in a single platform, eliminating separate tool subscriptions.
Per-user pricing at $9 monthly on Essential is competitive for small teams compared to buying separate CRM and PM tools.
Workflow automation builder operates across all modules without requiring code or developer resources.
Includes native financial tracking with invoices, expense logging, and project-level budget monitoring.
Free tier exists with no time limit, allowing teams to use the platform indefinitely for very small-scale operations.

Weaknesses

September 2025 shift to per-seat pricing increased costs for teams as user counts grew, angering long-term customers.
Interface design is described as old-school with no dark mode, and there is no native macOS desktop application.
Free plan limits contacts to 100 and blocks email sync, functioning more as a time-limited trial than a free product.
Steep onboarding and learning curve reported by multiple G2 and Capterra reviewers, slowing team adoption.
No native e-signature or contract signing feature, requiring third-party integrations that break the all-in-one value proposition.

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

	Flowlu Source	Nutshell Destination
Strengths	Combines CRM, project management, invoicing, and knowledge base in a single platform, eliminating separate tool subscriptions. Per-user pricing at $9 monthly on Essential is competitive for small teams compared to buying separate CRM and PM tools. Workflow automation builder operates across all modules without requiring code or developer resources. Includes native financial tracking with invoices, expense logging, and project-level budget monitoring. Free tier exists with no time limit, allowing teams to use the platform indefinitely for very small-scale operations.	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	September 2025 shift to per-seat pricing increased costs for teams as user counts grew, angering long-term customers. Interface design is described as old-school with no dark mode, and there is no native macOS desktop application. Free plan limits contacts to 100 and blocks email sync, functioning more as a time-limited trial than a free product. Steep onboarding and learning curve reported by multiple G2 and Capterra reviewers, slowing team adoption. No native e-signature or contract signing feature, requiring third-party integrations that break the all-in-one value proposition.	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?

Moderate CRM migration. 4 of 8 objects need a mapping; the rest are 1:1.

Overall complexity

Moderate migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Flowlu and Nutshell.

Object compatibility
C
4 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
Flowlu: Not publicly documented.
Data volume sensitivity
B
Flowlu 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 Flowlu 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

Flowlu

Nutshell

How Flowlu objects map to Nutshell

What specifically takes care here

Six steps for a successful Flowlu to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Flowlu to Nutshell migration cost

What are you migrating?

Frequently asked questions about Flowlu to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from Flowlu.
Land in Nutshell, intact.

Migrate from Flowlu 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

Flowlu

Nutshell

How Flowlu objects map to Nutshell

What specifically takes care here

Six steps for a successful Flowlu to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Flowlu to Nutshell migration cost

Frequently asked questions about Flowlu to Nutshell data migrations

Can't find your answer?

How long does a Flowlu to Nutshell migration take?

What happens to my Flowlu projects, tasks, and invoices?

Do Flowlu Workflows migrate to Nutshell?

What does a Flowlu to Nutshell migration typically cost?

What happens to my Flowlu custom fields?

Can we keep Nutshell as our CRM and use another tool for projects?

Does Nutshell offer migration assistance included with subscription?

Related migrations to explore

Move from Flowlu. Land in Nutshell, intact.

Move from Flowlu.
Land in Nutshell, intact.