What actually migrates from Merlin to Nutshell?

There are no native CRM records in Merlin to migrate—no Contacts, Companies, Opportunities, or Pipeline Stages exist in Merlin's data model. What does migrate: uploaded documents (PDF, PPT, Word) attach as files in Nutshell; conversation threads with identifiable business context become Notes linked to the relevant Contact, Company, or Opportunity; extracted person and company names from documents are created as new Nutshell Person and Company records with customer approval; image-generation outputs attach as files. Custom Properties and Tags do not exist in Merlin and therefore cannot migrate.

Why does Merlin to Nutshell migration require entity extraction?

Because Merlin is an AI assistant, not a CRM. It does not store contact or company records. Any business context that exists in Merlin lives inside uploaded documents or conversation text. To move that context into Nutshell, we parse the documents for person names, company names, email addresses, and deal references, then create the corresponding Nutshell records. This is a reconstruction step, not a direct export. The customer reviews and approves the proposed entity list before any Nutshell records are created.

How long does a Merlin to Nutshell migration take?

Most migrations land between two and four weeks for customers with under 500 documents and no entity extraction scope. Migrations requiring named-entity extraction from a large document corpus (over 500 files), manual conversation analysis for business context, or multi-user account reconciliation move to five to eight weeks because of the parsing, deduplication, and customer approval cycles. Timeline does not depend on Nutshell record volume since record creation in Nutshell via API is fast—the bottleneck is document parsing and entity approval on the Merlin side.

What does a Merlin to Nutshell migration typically cost?

Migrations under 500 documents with file-attachment-only scope (no entity extraction) land between $3,500 and $5,000. Projects requiring named-entity extraction, document corpus analysis, or multi-user account mapping move to $6,500-$9,500. Pricing is not based on Nutshell record count because the primary work is parsing and reconstruction from Merlin's artifacts. Nutshell subscription cost ($16-$67 per user per month) is separate from the migration fee.

Do Merlin Workflows or Automations migrate to Nutshell?

Merlin has no workflow or automation engine. There are no sequences, property-triggered automations, or engagement cadences in Merlin to inventory or migrate. Nutshell workflows and automation rules are scoped separately by the customer's admin post-migration. We do not create Nutshell workflows as part of the standard migration scope.

What happens to Merlin conversations after migration is complete?

Conversation text migrates as Notes in Nutshell if it references identifiable business entities. Thread-level metadata (which AI model answered each turn, token usage, response latency) does not migrate because Merlin does not export this data. If auditability of AI interactions is a compliance requirement, we advise capturing model-attribution screenshots from Merlin before export. Post-migration, the customer closes the Merlin account to stop new data accumulation.

Can FlitStack AI migrate from multiple Merlin user accounts into a single Nutshell account?

Yes. We can map multiple Merlin user exports (each user's conversation threads and uploaded documents) into a single Nutshell account. We resolve which Nutshell User each Merlin user's artifacts attach to, merge duplicate Person and Company records that appear across multiple Merlin users, and attach shared documents to the correct Nutshell records. The customer designates the owner assignment strategy during scoping.

How do you handle documents that exceed Merlin Free-tier limits?

During scoping we identify documents that may have been uploaded under the Free tier and truncated at 10 pages. If a customer was on Pro when uploading but the export shows a truncated file, we flag it and ask the customer to confirm whether a full-length version exists elsewhere. We cannot recover content that was never uploaded due to the Free-tier limit. Any truncated documents are noted in the migration inventory so the customer understands what is not present in Nutshell post-migration.

Merlin to Nutshell Migration — Field-Level Mapping & Rollback

Overview

What this migration involves

This migration is structurally distinct from standard CRM-to-CRM moves because Merlin is not a CRM—it has no Contacts, Companies, Opportunities, or Pipeline Stages to export. What Merlin does store is conversation threads, uploaded documents (PDF, PPT, Word), and image-generation outputs in user-scoped browser storage with no public API. We guide customers through the manual dashboard export, parse uploaded documents for any embedded business entities (person names, company names, deal references), create matching Nutshell records via the REST API, and attach the original document files to the correct Contact, Company, or Activity. We do not migrate workflows or automations because Merlin has no automation model to inventory. Nutshell workflows and any existing automations are scoped separately by the customer's admin post-import.

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

Merlin

What's pushing teams away

Usage caps on the free and Pro tiers create friction—users report hitting daily query limits mid-workday, prompting migration to platforms with higher or unmetered quotas.
Some users describe the initial setup and extension configuration as complicated, particularly when integrating with specific browsers or enterprise environments.
Privacy concerns arise when uploading sensitive business documents to a third-party AI platform, causing regulated-industry users to seek on-premise or compliance-certified alternatives.
The platform's lack of native integrations with enterprise tools like Slack, Notion, or Salesforce means teams relying on those ecosystems must work around gaps, driving some to more connected AI assistants.

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

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

Merlin

Uploaded Documents (PDF, PPT, Word)

maps to

Nutshell

Attachment (linked to Company, Person, or Opportunity)

1:1

Fully supported

We capture Merlin Document Chat uploads as binary file blobs and re-attach them in Nutshell via the API. Free-tier uploads capped at 10 pages are flagged during scoping; Pro-tier unlimited-length uploads migrate in full. Each file is linked to the relevant Nutshell record (Company, Person, or Opportunity) using ContentDocumentLink. If the customer cannot identify the intended record from document naming or content, the attachment is held in a reconciliation queue pending admin direction.

Merlin

Conversation Threads

maps to

Nutshell

Note (linked to Person or Company)

1:many

Fully supported

Merlin conversation text exports as structured thread output. We parse each thread for business context—if a thread references a person or company name that maps to a Nutshell record, the thread text becomes a Note linked to that record. Threads without identifiable business context are attached to the originating user record as a general Notes entry. Thread-level model attribution (which AI model responded per turn) is not exported from Merlin and cannot be preserved.

Merlin

User Account (email, plan tier, usage quota)

maps to

Nutshell

User

1:1

Fully supported

Merlin account metadata (email address, plan tier, Pro status) maps to Nutshell User records. Owner assignment in Merlin is not a first-class concept, so the customer designates which Merlin users map to which Nutshell User during scoping. If a Merlin user has no corresponding Nutshell seat, their documents and conversations are imported under a designated migration admin account and reassigned post-migration.

Merlin

Extracted Person Names (from document parsing)

maps to

Nutshell

Person (Contact)

many:1

Fully supported

This is a derived object: Merlin does not store Contacts, but uploaded documents may contain person names, email addresses, or titles. We perform entity extraction as a supplementary step, identify unique persons, and create Nutshell Person records. Multiple mentions of the same person across documents merge into a single Contact with the most complete name, email, and phone set retained. The customer reviews and approves the extracted person list before creation.

Merlin

Extracted Company Names (from document parsing)

maps to

Nutshell

Company

many:1

Fully supported

Like person extraction, Merlin documents may reference company names, domains, or organizations. We extract unique company names, create Nutshell Company records, and link any extracted Persons to their employer Company via the Person-Company relationship. Companies mentioned without any identified Persons are created as standalone Company records for the customer to populate.

Merlin

Image Generation Outputs

maps to

Nutshell

Attachment (linked to related record or User)

1:1

Fully supported

Merlin image-generation outputs (PNG/JPG) are stored as file attachments in Merlin's user storage. We preserve file type, creation date, and binary content and attach to the relevant Nutshell record if identifiable, or to the importing User record if not. Image context is inferred from conversation thread content when available.

Merlin

Custom Properties

maps to

Nutshell

Not applicable

1:1

Not supported

Merlin does not expose a schema for user-defined properties. Any structured metadata stored within Merlin beyond conversation text and file blobs is not accessible for export. We cannot migrate custom fields because none exist in Merlin's data model.

Merlin

Merlin	Nutshell	Compatibility
Uploaded Documents (PDF, PPT, Word)	Attachment (linked to Company, Person, or Opportunity)1:1	Fully supported
Conversation Threads	Note (linked to Person or Company)1:many	Fully supported
User Account (email, plan tier, usage quota)	User1:1	Fully supported
Extracted Person Names (from document parsing)	Person (Contact)many:1	Fully supported
Extracted Company Names (from document parsing)	Companymany:1	Fully supported
Image Generation Outputs	Attachment (linked to related record or User)1:1	Fully supported
Custom Properties	Not applicable1:1	Not supported
Tags	Not applicable1:1	Not supported

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.

Merlin gotchas

High

No public API for automated export

Medium

Document upload limit differences by tier are migration-critical

Medium

Conversation metadata is not exported

Low

No contacts or CRM objects means context must be rebuilt

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

Merlin gotchas		Nutshell gotchas
Severity	Issue	Severity	Issue
High	No public API for automated export	High	Contact tier limits enforced on import
Medium	Document upload limit differences by tier are migration-critical	Medium	No bulk API endpoint requires paginated extraction
Medium	Conversation metadata is not exported	Medium	Email sequences not exportable via API
Low	No contacts or CRM objects means context must be rebuilt	Medium	Foundation plan disables key sales features

Pair-specific challenges

No public API means migration requires manual export and browser-based capture

Merlin publishes no REST or GraphQL endpoint for accessing conversation history, uploaded documents, or account settings programmatically. We guide customers through the manual dashboard export process (downloading conversation exports and document files) and, where browser storage is accessible, we capture session data for structured parsing. This is not an automated pull—it depends on customer cooperation and browser session state. Any export must be completed before account closure because Merlin does not guarantee access post-cancellation.
Free-tier document truncation must be identified before export

Merlin Free users are capped at 10-page uploads in Document Chat. Pro users have unlimited document length. When migrating from Merlin as a source, we flag any documents that may have been uploaded under the Free tier and therefore truncated at 10 pages. Customers on Pro who uploaded documents exceeding the Free limit need to confirm those documents were processed under Pro to ensure full content is available for export. We check document size and page estimates against tier during scoping.
Entity extraction from documents requires customer approval before record creation

Because Merlin stores no Contacts or Companies natively, any person or company data in Nutshell must be derived from document parsing and conversation analysis. We perform named-entity extraction as a supplementary migration step, but extracted entities require customer sign-off before we create records in Nutshell. False-positive extractions (a person's name appearing in a legal clause versus a real contact) are the customer's domain knowledge to correct, not ours. We deliver the proposed entity list with source citations before creation.
Conversation model attribution and token usage metadata is permanently lost in export

Merlin's export covers conversation text and timestamps but does not include per-turn model attribution (which AI model answered which turn), token usage, or latency metadata. For customers who need to audit AI decision trails, track per-model usage costs, or reproduce specific AI outputs, this metadata is permanently unavailable. We flag this gap during scoping and advise customers to capture model-attribution screenshots if auditability or compliance requirements depend on it.

Migration approach

Six steps for a successful Merlin to Nutshell data migration

Manual export guidance and scoping session

We guide the customer through Merlin's dashboard export process to download conversation history and document files. We also provide instructions for capturing browser local storage if the dashboard export does not include full document content. During scoping, we audit the export volume (number of conversations, document count, file sizes), identify which documents were uploaded under Free tier (subject to the 10-page cap), and determine whether entity extraction is in scope. We deliver a written migration scope document before any parsing begins.
Document parsing and entity extraction

We parse all exported documents (PDF, PPT, Word) using structured text extraction. For each document, we identify and extract person names, company names, email addresses, phone numbers, and any deal or project references. Extracted entities are deduplicated and grouped. We deliver a proposed entity list to the customer for review and approval. Any entities the customer marks as non-business (e.g., names appearing in legal boilerplate) are excluded from Nutshell record creation.
Nutshell schema preparation

We review the customer's Nutshell account to confirm which tiers and objects are active (Leads enabled vs. Contacts only, Products catalog, custom fields). We identify any required Nutshell configuration—such as enabling Leads if the customer wants a distinction between unqualified prospects and qualified contacts—before record creation. We do not modify Nutshell's pipeline stages, custom fields, or workflow rules as part of the standard migration scope; these are pre-migration setup tasks for the customer's Nutshell admin.
Entity creation and document attachment via Nutshell API

We create Nutshell Company records first (parent objects), then Person records linked to their Company via the Person-Company relationship, then any relevant Opportunity records if deal context was extractable from documents. All exported files are attached as Nutshell Attachments linked to the appropriate Company, Person, or Opportunity via ContentDocumentLink. Conversation threads that reference identifiable business entities become Notes attached to the relevant record. We resolve the importing User account for all records and flag any owner assignment that requires admin decision.
Validation, reconciliation, and cutover handoff

We generate a row-count reconciliation report showing entities extracted, entities approved, Nutshell records created, and documents attached. The customer spot-checks 20-30 records against the original Merlin export to confirm accuracy. Any mapping errors are corrected before the final delta pass. We deliver a written inventory of conversation threads that could not be linked to a specific record (with file location) for the customer to route manually. Nutshell becomes the system of record upon customer sign-off, and the Merlin account is scheduled for closure.

Platform deep dives

Context on both ends of the pair

Merlin

Source

Strengths

Single extension surfaces 70+ AI models without requiring multiple subscriptions or browser tabs.
Document Chat supports PDF, PowerPoint, and Word with Q&A capabilities across all three formats.
Google Search integration delivers AI summaries inline with web results, supporting continuous research workflows.
Image generation is built in, reducing the need for a separate AI image tool for basic use cases.
Free tier provides functional access to core features without requiring credit card information upfront.

Weaknesses

No public API documented for programmatic access, automation, or third-party integration, limiting enterprise and developer adoption.
Usage-based pricing at $100/month equivalent on Pro tier does not align with flat-seat pricing expectations of SaaS buyers.
No native CRM, helpdesk, or project management data model—Merlin does not store contacts, deals, tickets, or tasks as structured objects.
Document upload limits and daily query caps are not clearly communicated in the interface, leading to mid-session interruptions.
No support for team collaboration features such as shared workspaces, team-wide usage dashboards, or role-based access controls.

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

	Merlin Source	Nutshell Destination
Strengths	Single extension surfaces 70+ AI models without requiring multiple subscriptions or browser tabs. Document Chat supports PDF, PowerPoint, and Word with Q&A capabilities across all three formats. Google Search integration delivers AI summaries inline with web results, supporting continuous research workflows. Image generation is built in, reducing the need for a separate AI image tool for basic use cases. Free tier provides functional access to core features without requiring credit card information upfront.	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	No public API documented for programmatic access, automation, or third-party integration, limiting enterprise and developer adoption. Usage-based pricing at $100/month equivalent on Pro tier does not align with flat-seat pricing expectations of SaaS buyers. No native CRM, helpdesk, or project management data model—Merlin does not store contacts, deals, tickets, or tasks as structured objects. Document upload limits and daily query caps are not clearly communicated in the interface, leading to mid-session interruptions. No support for team collaboration features such as shared workspaces, team-wide usage dashboards, or role-based access controls.	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. 1 of 8 objects need a manual workaround.

Overall complexity

Standard migration

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

Object compatibility
B
1 of 8 objects need a manual workaround.
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
Merlin: Not publicly documented.
Data volume sensitivity
B
Merlin 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 Merlin 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

Merlin

Nutshell

How Merlin objects map to Nutshell

What specifically takes care here

Six steps for a successful Merlin to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Merlin to Nutshell migration cost

What are you migrating?

Frequently asked questions about Merlin to Nutshell data migrations

Can't find your answer?

Related migrations to explore

Move from Merlin.
Land in Nutshell, intact.

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

Merlin

Nutshell

How Merlin objects map to Nutshell

What specifically takes care here

Six steps for a successful Merlin to Nutshell data migration

Context on both ends of the pair

How hard is this migration?

Estimate your Merlin to Nutshell migration cost

Frequently asked questions about Merlin to Nutshell data migrations

Can't find your answer?

What actually migrates from Merlin to Nutshell?

Why does Merlin to Nutshell migration require entity extraction?

How long does a Merlin to Nutshell migration take?

What does a Merlin to Nutshell migration typically cost?

Do Merlin Workflows or Automations migrate to Nutshell?

What happens to Merlin conversations after migration is complete?

Can FlitStack AI migrate from multiple Merlin user accounts into a single Nutshell account?

How do you handle documents that exceed Merlin Free-tier limits?

Related migrations to explore

Move from Merlin. Land in Nutshell, intact.

Move from Merlin.
Land in Nutshell, intact.