CRM migration
Field-level mapping, validation, and rollback between Flash Lead Sales and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Flash Lead Sales
Source
Nutshell
Destination
Compatibility
6 of 9
objects map 1:1 between Flash Lead Sales and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
Flash Lead Sales stores leads with custom stages, tags, and source attribution, but it provides no public API — migration depends entirely on the platform's built-in CSV export. We work directly with the customer's exported files, reconstructing stage progression from activity logs where the current stage is the only guaranteed discrete field, and mapping each user-defined pipeline stage to a Nutshell stage before import. We preserve tags, lead sources, owner assignments, and social message thread logs as contact notes. Custom pipeline stages and role-based team hierarchies require explicit configuration mapping at scoping. Automations and reporting dashboards do not migrate; we deliver a written inventory of automation triggers and logic for the customer's admin to rebuild in Nutshell.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Flash Lead Sales 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.
Flash Lead Sales
Lead
Nutshell
Person or Lead
1:1Flash Lead's primary record is the Lead object with source, tags, stage, owner, and history. In Nutshell, Leads represent unqualified prospects and Persons represent qualified contacts. We ask the customer during scoping whether Flash Lead leads should map to Nutshell Leads (if they represent raw prospect intake from Facebook) or Persons (if the team uses Flash Lead as a full contact database). Tags and lead sources migrate as custom properties on the target record.
Flash Lead Sales
Contact
Nutshell
Person
1:1Flash Lead Contacts (customer profiles with purchase history and location) map directly to Nutshell Person records. We use email address as the dedupe key during import. If Flash Lead stores a contact without an email, we flag those records for manual review and attach any available phone number for matching in Nutshell.
Flash Lead Sales
Pipeline Stage
Nutshell
Stage
lossyFlash Lead pipeline stages are user-defined with no enforced schema, and stage transitions are recorded as activity log entries rather than discrete fields. We extract the full activity log during scoping, identify every stage transition timestamp, and reconstruct the progression as a stage history note on the Nutshell deal. Current stage maps directly to Nutshell's stage field. The customer reviews and approves the stage mapping table before migration.
Flash Lead Sales
Deal (on Pro tier)
Nutshell
Lead
1:1Flash Lead Pro includes invoicing and deal tracking tied to leads. These map to Nutshell Lead records with the deal amount preserved as a custom field. If the customer uses Flash Lead's invoicing to track closed-won revenue, we flag those records for review because Nutshell does not have a native invoice object on its standard plans.
Flash Lead Sales
Team Member
Nutshell
User
1:1Flash Lead Team Members with role-based access map to Nutshell User accounts. Owner assignment on leads is preserved by matching on email address. We extract the role hierarchy from Flash Lead and document it for the customer's admin to configure Nutshell's sharing rules and team visibility settings post-migration.
Flash Lead Sales
Tag
Nutshell
Custom property (multi-select or text)
lossyTags in Flash Lead are applied without limit to leads for segmentation. We export all tags as a comma-separated list and import them as a custom text property on the Nutshell Lead or Person record. If the customer uses more than 20 distinct tags, we recommend a dedicated custom field with type-ahead rather than a freeform text block.
Flash Lead Sales
Lead Source
Nutshell
Custom property
1:1Lead sources (Facebook, Instagram, Referral, Purchased List, etc.) track where leads originated. We preserve source labels as a custom property on the Lead record in Nutshell. This field is used for pipeline reporting by source once migration is complete.
Flash Lead Sales
Social Message Thread
Nutshell
Note on Person
1:1Facebook Messenger and Instagram DMs are stored in Flash Lead as conversation text logs attached to contact records. Thread branching, timestamps, and read receipts do not export. We attach the full conversation text as a Note on the corresponding Nutshell Person record and note the limitation in the migration report so the customer can assess whether conversation history is business-critical for their use case.
Flash Lead Sales
Invoice (Pro tier)
Nutshell
Custom field or attachment
lossyFlash Lead Pro invoicing records (amount, status, related deal) are extracted where they exist. Nutshell's standard plans do not include a native invoice object. We import invoice amount and status as custom fields on the Lead record and attach any exported invoice PDF as a file on the record. The customer evaluates whether a dedicated invoicing tool (QuickBooks, Zoho Invoice) is needed post-migration.
| Flash Lead Sales | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | Person or Lead1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Pipeline Stage | Stagelossy | Fully supported | |
| Deal (on Pro tier) | Lead1:1 | Fully supported | |
| Team Member | User1:1 | Fully supported | |
| Tag | Custom property (multi-select or text)lossy | Fully supported | |
| Lead Source | Custom property1:1 | Fully supported | |
| Social Message Thread | Note on Person1:1 | Fully supported | |
| Invoice (Pro tier) | Custom field or attachmentlossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Flash Lead Sales gotchas
No documented public API for programmatic export
Lead stage history stored as activity log rather than discrete fields
Custom pipeline stages require explicit mapping per account
Social message threads export as flat text without thread structure
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
Discovery and CSV export audit
We request all available CSV exports from the Flash Lead account: leads, contacts, pipeline stages, team members, tags, lead sources, and any available activity logs or social message exports. We audit the exports for completeness, flag any missing fields (particularly stage history and source attribution), and ask the customer to re-export with all columns selected if gaps are found. We also extract the full list of user-defined pipeline stages and their probabilities for the mapping table.
Stage history reconstruction and mapping table
We parse the Flash Lead activity log export to identify every stage transition recorded against each lead. We reconstruct the progression as a timeline note on each record. We then produce the stage mapping table: each Flash Lead stage name is explicitly assigned to a Nutshell stage name (existing or newly created). The customer reviews and approves the mapping before any import begins.
Nutshell account setup and custom field configuration
We configure Nutshell's pipeline: creating stages that match the approved mapping table, setting probability percentages per stage, and configuring any custom properties needed for tags, lead sources, and stage history notes. We set up team visibility and sharing rules based on the Flash Lead role hierarchy documented during discovery.
Owner reconciliation and user provisioning
We extract every distinct owner referenced on Flash Lead records and match by email against the Nutshell destination account's user list. Any Flash Lead owner without a matching Nutshell user is added to a reconciliation queue for the customer's admin to provision before record import resumes.
Production import in dependency order
We run production migration in record-dependency order: Persons (from Flash Lead Contacts), Leads (with stage history notes attached), custom property values (tags and sources), social message logs (as Notes on Person records), and team member role assignments (as sharing rule documentation). Each phase emits a row-count reconciliation report before the next phase begins.
Cutover, validation, and automation handoff
We freeze Flash Lead 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 inventory document to the customer's admin team. We support a one-week hypercare window to resolve reconciliation issues raised by the sales team. We do not rebuild Flash Lead automations as Nutshell workflow rules inside the migration scope; that is a separate task for the customer's admin.
Platform deep dives
Flash Lead Sales
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 1 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 Flash Lead Sales and Nutshell.
Object compatibility
1 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Flash Lead Sales: Not publicly documented.
Data volume sensitivity
Flash Lead Sales doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Flash Lead Sales to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Flash Lead Sales to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Flash Lead Sales
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.