CRM migration

Migrate from Followup CRM to Nutshell

Field-level mapping, validation, and rollback between Followup CRM and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Followup CRM logo

Followup CRM

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

10 of 10

objects map 1:1 between Followup CRM and Nutshell.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

FollowUp CRM stores contacts, companies, bids, and projects in a construction-focused data model with custom fields for bid tracking, goals, and quota management. Nutshell uses a standard SMB CRM schema with People (contacts), Companies, Leads, Deals, and Activities — custom fields attach to each record type. FlitStack AI extracts your FollowUp CRM data via API, maps bids and projects to Nutshell Deals with custom field preservation, resolves owner email addresses to Nutshell users, and migrates activity history as Tasks and Notes. We do not migrate FollowUp CRM workflows, automation rules, or bid-specific calculation logic — those rebuild as Nutshell sequences and custom fields. The migration runs in three phases: sample diff, full data transfer, and a 48-hour delta pickup that captures any records modified during cutover. Nutshell's 100-contact free trial Foundation tier and $13–79/user/month pricing structure means teams can validate the migrated data before committing to a full account, ensuring a smooth transition without hidden costs.

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

Followup CRM logo

Followup CRM

What's pushing teams away

  • Starting price of ~$4500/yr for 5 users is steep for small contractors and locks teams into annual contracts before validating fit.
  • No publicly documented API or bulk export endpoints makes migration to another platform technically difficult without vendor assistance.
  • Known duplicate follow-up issue in the system frustrates users who rely on clean task queues for sales cadence.
  • Construction-specific feature set does not generalize well; teams outgrowing the niche find limited upgrade paths within the platform.

Choosing

Nutshell logo

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

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

Followup CRM

Contact

maps to

Nutshell

Person

1:1
Fully supported

FollowUp CRM contacts map 1:1 to Nutshell People. The Person record in Nutshell holds name, email, phone, title, address, and custom fields. Owner resolution uses email match against Nutshell user accounts — unmatched owners flag before migration so you can invite them or assign a fallback.

Followup CRM

Company

maps to

Nutshell

Company

1:1
Fully supported

FollowUp CRM company records map to Nutshell Companies with name, domain, industry, employee count, and annual revenue. If a contact in FollowUp CRM has no associated company, it lands in Nutshell as a standalone Person without a Company link — no forced 'Unassigned' account required.

Followup CRM

Bid

maps to

Nutshell

Deal

1:1
Fully supported

FollowUp CRM bids (with bid amount, stage, and load-order) map to Nutshell Deals. Bid stage names map via value_mapping to Nutshell Deal stage values. The bid's load-order sequence preserves in a custom integer field (Bid_Load_Order__c) since Nutshell Deal ordering is drag-and-drop by stage, not a global sequence number.

Followup CRM

Project

maps to

Nutshell

Deal

1:1
Fully supported

FollowUp CRM projects (construction project tracking linked to bids) map to Nutshell Deals with project name, status, and custom fields. Project-specific data like phase completion or site address migrates to custom fields on the Deal record. Projects without a bid link still create a Nutshell Deal — you choose the default stage in the mapping plan.

Followup CRM

Custom Field (Project-level, Dropdown)

maps to

Nutshell

Custom Field (Deal-level)

1:1
Fully supported

FollowUp CRM dropdown custom fields on Projects map to Nutshell custom fields on Deals with the same pick-list values. If Nutshell's default values differ, we create a value-mapping table during the planning phase. Dropdown options with no Nutshell equivalent get flagged for your admin to resolve before migration runs.

Followup CRM

Activity (Email)

maps to

Nutshell

Task

1:1
Fully supported

FollowUp CRM email activities (logged emails, open/click tracking) migrate as Nutshell Tasks with Type='Email'. Original timestamp, owner, and associated contact/company links preserve. Nutshell's Engagement email tracking (Pro/Business) will overwrite engagement data for emails sent after go-live — historical engagement history from FollowUp CRM stays as Tasks.

Followup CRM

Activity (Call)

maps to

Nutshell

Task

1:1
Fully supported

FollowUp CRM call logs (call duration, outcome, notes) migrate as Nutshell Tasks with Type='Call'. Call owner resolves by email match. If FollowUp CRM records call outcome in a custom field, that value maps to the Task's Description or a custom field on the Task.

Followup CRM

Activity (Note)

maps to

Nutshell

Note

1:1
Fully supported

FollowUp CRM notes map to Nutshell Notes with original create date, author, and linked record (Person or Company). Rich-text formatting in FollowUp CRM notes converts to plain text in Nutshell Notes. Attachments on FollowUp CRM notes download and re-upload to Nutshell Files linked to the Note record.

Followup CRM

Goal / Quota

maps to

Nutshell

Custom Field + Report

1:1
Fully supported

FollowUp CRM goals and team quotas have no direct Nutshell equivalent. We export goal definitions as a CSV reference file for your admin to rebuild using Nutshell's reporting module or a connected BI tool. The goal data itself (historical quota achievement) can optionally migrate as read-only custom fields on Person records.

Followup CRM

Attachment (File on Bid/Project)

maps to

Nutshell

File

1:1
Fully supported

FollowUp CRM file attachments on bids and projects download and re-upload to Nutshell Files linked to the corresponding Deal record. File size limits follow Nutshell's 25MB per-file constraint — files over 25MB get split or skipped with a flag in the migration report. Original upload date and uploader name preserve in the file metadata.

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.

Followup CRM logo

Followup CRM gotchas

High

No documented API or bulk export endpoint

Medium

Duplicate follow-up artifacts in contact records

Medium

Annual contract pricing creates migration timing pressure

Low

Custom fields require explicit field-level mapping

Nutshell logo

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

Pair-specific challenges

  • Bid load-order sequencing has no native Nutshell equivalent

    FollowUp CRM uses a load-order field (starting at 11 for custom fields) to sequence bids in the project view. Nutshell Deal ordering is drag-and-drop within a pipeline stage — there is no global sequence number field. FlitStack AI preserves the load-order value in a custom integer field (Bid_Load_Order__c) on the Nutshell Deal record. Your team can use this field to sort deals in a custom Nutshell report during the transition period, or your admin can manually reorder the Nutshell pipeline once migration completes. The custom field approach is a temporary bridge, not a permanent substitute for Nutshell's native drag-and-drop model.

  • Goals and quota data cannot migrate as live tracking fields

    FollowUp CRM's goal and quota tracking lives in the dashboard as a calculated metric tied to user assignments and bid-stage probabilities. Nutshell has no native goal/quota module — the closest equivalent is Nutshell Analytics (a paid add-on) or a custom report built from Deal fields. FlitStack AI exports your current goal definitions and historical quota-achievement data as a CSV reference file. To rebuild goal tracking in Nutshell, your admin configures Deal-stage probabilities that align with your quota targets, then uses Nutshell's reporting or a connected BI tool to surface quota attainment. This is a manual rebuild step, not a data migration.

  • FollowUp CRM's project-bid linkage requires manual reconstruction

    FollowUp CRM links Projects to Bids as parent-child records, allowing users to view all bids associated with a single construction project. Nutshell Deals have a single level of granularity — there is no native parent-Deal / child-Deal hierarchy. FlitStack AI migrates each FollowUp CRM Project as an independent Nutshell Deal, and each Bid as a separate Nutshell Deal. If you need to preserve the project-bid relationship, we create a custom text field (Related_Project_Bid_ID__c) on both records so your team can link them via a custom report or filter. Rebuilding a true project tracking view requires Nutshell's custom reporting or a connected project management tool.

  • Contact-level custom fields with User type have no direct Nutshell equivalent

    FollowUp CRM allows custom fields of type 'User' on Project records, enabling dropdowns that reference other FollowUp CRM users (e.g., Assigned Estimator). Nutshell custom fields on Deals support text, number, date, and pick-list types but do not have a native 'User reference' type. FollowUp CRM User-type custom fields migrate as pick-list custom fields in Nutshell with the user display names as options. If a referenced FollowUp CRM user does not have a corresponding Nutshell account, their name still migrates as a static pick-list value — you manually update it if the Nutshell user account is created later.

Migration approach

Six steps for a successful Followup CRM to Nutshell data migration

  1. Extract FollowUp CRM data via API

    FlitStack AI connects to your FollowUp CRM instance using scoped read-only API credentials. We extract all People (contacts), Companies, Bids, Projects, custom field definitions, activity history (emails, calls, notes), and file attachments. The extraction runs with read-only access — your team continues working in FollowUp CRM throughout the process. A data extraction manifest (record counts by object, custom field inventory) is generated before mapping begins.

  2. Map objects and fields with bid-stage and project-status value tables

    We build an object-and-field mapping plan that covers all 10 standard mappings and any FollowUp CRM custom fields. Bid stages and project statuses map via value-by-value tables — you confirm each mapping during the planning review. Owner email addresses are matched against a list of your target Nutshell user accounts. Any FollowUp CRM users without Nutshell accounts are flagged with a fallback owner assignment (e.g., admin account) so no record lands without an owner.

  3. Run a sample migration with field-level diff

    A representative slice of 100–500 records migrates first, spanning contacts, companies, bids, and activities. We generate a field-level diff report showing the source value, mapped value, and any transformation notes for each field. You review the diff in your Nutshell sandbox (or trial account) and approve or request adjustments to the mapping plan before the full run commits. Bid load-order values and project custom fields are verified against your expected sequence during this review.

  4. Execute full migration with delta-pickup window

    Once the mapping plan is approved, the full migration runs against your Nutshell production account. A delta-pickup window of 24–48 hours after the initial load captures any records created or modified in FollowUp CRM during the cutover. Audit logs record every operation — record count, owner assignment, field-level mapping, and any records skipped due to attachment size limits. One-click rollback is available if reconciliation identifies missing or misaligned data.

Platform deep dives

Context on both ends of the pair

Followup CRM logo

Followup CRM

Source

Strengths

  • Intuitive drag-and-drop contact and field configuration requiring no developer involvement.
  • Built-in bid volume tracking and quotas aligned with construction sales workflows.
  • Responsive customer support praised across G2 review community.
  • Custom reporting exports from Project Pages including bid-to Excel formats.
  • Goals and team performance tracking features built into the home page dashboard.

Weaknesses

  • No publicly documented API makes programmatic migration difficult without vendor cooperation.
  • Annual contract requirement at ~$4500/yr for 5 users locks in spend before full validation.
  • Known duplicate follow-up bug creates dirty data requiring manual cleanup before migration.
  • Limited integrations beyond Procore make ecosystem connectivity a constraint for some construction firms.
Nutshell logo

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

Complexity grading

How hard is this migration?

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

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Followup 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

    Followup CRM: Not publicly documented.

  • Data volume sensitivity

    B

    Followup CRM doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Followup CRM to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Followup CRM to Nutshell data migrations

Answers to the questions buyers ask most during Followup CRM to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Followup CRM to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most FollowUp CRM to Nutshell migrations complete within 48–72 hours for datasets under 50,000 total records. The longest step is planning and approving the bid-stage and project-status value-mapping tables — that review typically takes 1–2 business days on your end. Migrations exceeding 500,000 records or involving heavy attachment libraries extend to 5–7 days. Nutshell's API rate limits (1,000 requests per minute on Business plans) are respected during the load to avoid throttling.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Followup CRM.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day