CRM migration

Migrate from Workbooks to Freshsales

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

Workbooks logo

Workbooks

Source

Freshsales

Destination

Freshsales logo

Compatibility

90%

9 of 10

objects map 1:1 between Workbooks and Freshsales.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Workbooks CRM to Freshsales requires reconciling two different account-contact models. Workbooks treats Organisations and People as the primary pair with People linked to Organisations via a lookup; Freshsales uses Accounts and Contacts with an optional separate Lead object for pre-qualified prospects. We extract Workbooks Organisations and map them to Freshsales Accounts, preserving address and classification data. Workbooks People migrate to Freshsales Contacts linked to the Account by domain match or manual review. Opportunities, Cases, Activities, and any Quotations present on Workbooks Business tier migrate as Deals, Cases, and timeline records respectively. Custom fields require manual enumeration per record type because Workbooks deployments vary; we request read-only admin access during scoping to capture every bespoke field. We do not migrate Workbooks Workflows or Automation rules as code, and we do not move Quotations or Invoices if the source subscription is below the Business tier. The migration delivers a written inventory of any Workflows requiring rebuild in Freshsales Workflow Builder.

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

Workbooks logo

Workbooks

What's pushing teams away

  • Record save times degrade noticeably as the database grows, pushing teams with large transaction histories toward faster alternatives.
  • The UI has not kept pace with modern CRM expectations—younger sales staff find the navigation and visual design dated compared to HubSpot or Pipedrive.
  • Documentation and training materials are sparse, creating a steep onboarding curve for new users who are not power users.
  • Customisation options exist but the workflow for implementing them is non-obvious, leading to frustration when basic process changes require admin involvement.

Choosing

Freshsales logo

Freshsales

What's pulling them in

  • Lowest barrier to entry among major CRMs — the free tier supports up to 3 users and includes core CRM functionality before committing to per-seat pricing.
  • Built-in chat, email, and phone reduce reliance on third-party integrations for basic sales communication and contact management.
  • Freddy AI contact scoring and deal insights are included on Pro plans at a lower price than comparable HubSpot tiers.
  • Kanban pipeline views across Contacts, Accounts, and Deals provide visual deal management without requiring custom configuration.
  • Integration with the broader Freshworks ecosystem (Freshdesk, Freshchat, Freshservice) reduces tool sprawl for teams already using Freshworks.

Object mapping

How Workbooks objects map to Freshsales

Each row shows how a Workbooks object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.

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

Workbooks

Organisation

maps to

Freshsales

Account

1:1
Fully supported

Workbooks Organisation records map directly to Freshsales Accounts. We extract the organisation name, all address fields (billing and shipping if populated), industry classification, phone, website, and any custom fields defined on the Organisation record type. The organisation name becomes the Account Name field; the domain extracted from the website field is stored for deduplication against existing Freshsales Accounts. If Workbooks stores multiple addresses per Organisation, the primary billing address migrates as the Account address with subsequent addresses preserved as notes.

Workbooks

Person

maps to

Freshsales

Contact

1:1
Fully supported

Workbooks People map to Freshsales Contacts linked to the parent Account. The Organisation lookup on the Person record resolves to the Freshsales AccountId by name match (or domain match if website is populated on both sides). We extract salutation, first name, last name, job title, phone, mobile, email, and any custom fields defined on the Person record type. People without a linked Organisation migrate as standalone Contacts; the customer reviews these during reconciliation to assign them to the correct Account.

Workbooks

Opportunity

maps to

Freshsales

Deal

1:1
Fully supported

Workbooks Opportunities map to Freshsales Deals. Stage name, probability percentage, and expected close date migrate directly. Deal value migrates to Freshsales Amount. Owner assignment resolves by email match against the Freshsales User table; unresolved owners go to a reconciliation queue for the customer admin to provision. Pipeline stage mapping is defined during scoping and deployed as Freshsales stage configuration before migration begins.

Workbooks

Case

maps to

Freshsales

Case

1:1
Fully supported

Workbooks Cases migrate to Freshsales Case records. We extract case subject, description, status (New, Open, Pending, Resolved, Closed), priority (Low, Medium, High, Urgent), assigned user, related Organisation, and all case activities. Open cases and resolved cases both migrate; resolved case history is preserved for audit purposes. Case number is stored as a custom field if the customer requires traceability back to the original Workbooks identifier.

Workbooks

Quotation

maps to

Freshsales

Deal Line Item or Note

1:1
Fully supported

Quotations exist only on Workbooks Business and Business Pro tiers. If the source subscription is on CRM or CRM Pro, Quotation objects are absent and this step is skipped. For Business-tier sources, we extract quotation headers (related Organisation, owner, validity date) and line items (product name, quantity, unit price, discount). Line items migrate as custom fields on the Freshsales Deal or as attached notes if the destination plan does not include a native quoting module. We flag Configure, Price, Quote as a Freshsales Pro add-on ($19/user/mo) if the customer wants native quote management post-migration.

Workbooks

Invoice

maps to

Freshsales

Note or Custom Field

1:1
Fully supported

Invoices are available on Workbooks Business and Business Pro tiers only. We extract invoice header data, line items, payment status, and credit note associations. Invoices do not have a native Freshsales equivalent; invoice metadata migrates as a note attached to the related Account or Deal, or as custom fields if the customer prefers structured data. The customer admin reviews and reconciles invoice records post-migration with a recommended accounting tool integration (Freshbooks, Xero, or QuickBooks).

Workbooks

Activity (Call, Email, Meeting, Task)

maps to

Freshsales

Activity (Task, Event)

1:1
Fully supported

Workbooks Activities (logged calls, emails, meetings, and tasks) linked to an Organisation or Person migrate to Freshsales Activity records attached to the Contact or Account. Call duration and disposition migrate to custom Task fields. Meeting start and end times migrate to Freshsales Event records. Email subject and body migrate as Task records with activity type recorded. Each Activity is linked to the migrated Contact by email address or name match against the Freshsales Contact table.

Workbooks

Custom Fields

maps to

Freshsales

Custom Fields

lossy
Mapping required

Workbooks deployments vary significantly in which custom fields exist and what they are called per record type. We request read-only admin access during scoping and enumerate custom fields on Organisation, Person, Opportunity, Case, Quotation, and Invoice record types before writing the migration spec. Each Workbooks custom field maps to a Freshsales custom field of equivalent type: text to text, number to number, date to date, dropdown to picklist, checkbox to checkbox. iFrame fields (URL strings only) migrate as text fields. File upload fields require separate binary extraction and attachment handling.

Workbooks

Lead

maps to

Freshsales

Lead

1:1
Fully supported

Workbooks Lead records hold pre-conversion prospect data with lead source, status, rating, and assigned owner. These map directly to Freshsales Lead records. Lead status in Workbooks maps to Freshsales Lead Status; lead score maps to a custom numeric field if present. After migration, Freshsales Lead Conversion creates a Contact and Account from the Lead. The original Workbooks Lead status is preserved in a custom field for audit.

Workbooks

Campaign

maps to

Freshsales

Campaign

1:1
Fully supported

Workbooks Campaigns migrate to Freshsales Campaigns. Campaign name, status (Active, Paused, Completed), start and end dates, and budgeted cost migrate. Campaign memberships (which People are in which Campaign) migrate as Campaign Member records linked to the migrated Contact or Lead. Campaign response data migrates as custom fields if the customer requires historical marketing attribution.

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.

Workbooks logo

Workbooks gotchas

High

Record save latency on large datasets

Medium

Custom Fields require manual field-level mapping

Medium

Quotation and Invoice exports require Business tier

Low

iFrame custom fields export as URL strings only

Freshsales logo

Freshsales gotchas

Medium

Freddy AI is Pro-tier only despite heavy marketing

High

Post-migration emails and sequences are disabled

Medium

Bot session credits are a one-time 500-session allocation

Medium

Phone credits charged per minute with no cap

Low

File storage limits scale with plan tier

Pair-specific challenges

  • Quotation and Invoice objects absent on non-Business tiers

    Workbooks CRM and CRM Pro tiers do not include Quotation, Invoice, or Order objects. If the source subscription is on one of these tiers, these objects do not exist in the data export and the migration scope excludes them. We confirm the source account tier during scoping before finalising the object list. If the customer requires quotation data, they must upgrade to Business tier on Workbooks before export or accept that quotes are not available to migrate.

  • Custom field enumeration requires read-only admin access

    Workbooks does not provide a unified schema export listing every custom field across all record types. Each Workbooks deployment has a different set of custom fields based on admin configuration. We request read-only admin access during scoping to enumerate custom fields per record type (Organisation, Person, Opportunity, Case, Quotation) before writing the migration spec. Skipping this step silently drops bespoke data that the customer expects to migrate.

  • Freshsales API rate limits cap write throughput

    Freshsales enforces hourly API rate limits by plan tier: Growth at 1,000 requests per hour, Pro at 2,000, and Enterprise at 5,000 with an add-on available for higher limits. Workbooks does not publish its own API rate limits; we batch exports at 5,000-record intervals. During the Freshsales import phase, we throttle writes to stay within the destination plan limit using exponential backoff. Large migrations (over 50,000 records) may require multi-day import windows or an Enterprise-tier plan with a higher rate-limit add-on.

  • Lead-to-Contact conversion mapping requires pre-planning

    Freshsales supports Lead conversion to Contact and Account with field-level mapping during conversion. Workbooks Lead records have custom fields that must map to Freshsales Contact or Account custom fields at conversion time. We configure the Freshsales Conversion Settings during the setup phase so that any Lead that is converted post-migration preserves its custom field data. If the conversion mapping is not pre-configured, custom field values are silently dropped on Lead conversion.

  • Workbooks Workflows and Automation rules do not migrate

    Workbooks Workflows and Automation rules are not data objects and cannot be extracted as records. They do not have a Freshsales equivalent in migration scope. We deliver a written inventory of every active Workbooks Workflow with its trigger, conditions, and actions for the customer admin to rebuild in Freshsales Workflow Builder. Quotations, sequences, and lead scoring rules similarly do not migrate; they are documented for manual rebuild.

Migration approach

Six steps for a successful Workbooks to Freshsales data migration

  1. Discovery and tier verification

    We audit the Workbooks subscription tier to confirm whether Quotation, Invoice, and Order objects are present. We enumerate record counts per object type (Organisations, People, Opportunities, Cases, Activities, Leads, Campaigns) and flag any custom fields requiring mapping by requesting read-only admin access. We review the destination Freshsales plan tier to confirm API rate limits and whether the Configure, Price, Quote add-on is required. The discovery output is a written migration scope document with record counts, object list, and a Freshsales plan recommendation.

  2. Custom field enumeration and mapping spec

    We log into Workbooks with read-only admin access and enumerate every custom field on Organisation, Person, Opportunity, Case, Quotation, and Invoice record types. We capture field name, field type, and any picklist values. We map each Workbooks custom field to a Freshsales custom field of equivalent type and note any transformation logic (date format normalisation, picklist value mapping, iFrame URL preservation). The mapping spec is shared with the customer for review and sign-off before any export begins.

  3. Freshsales sandbox setup and schema pre-creation

    We configure the destination Freshsales account with the required custom fields, stage values for Deals, case priorities and statuses, and any required add-ons (CPQ if in scope). We run a test import of a representative sample (typically 100-500 records per object) into a Freshsales sandbox or trial environment to validate the mapping spec and confirm that all fields land correctly. The customer reviews the test output and signs off before production migration begins.

  4. Data extraction from Workbooks

    We extract data from Workbooks in dependency order. Organisations export first as the parent records for Account creation. People export second with the Organisation lookup preserved for AccountId resolution. Opportunities, Cases, Activities, Leads, Campaigns, and Quotation or Invoice records export in subsequent phases. Exports run in batches of 5,000 records to avoid Workbooks save latency issues. Each batch is validated against the source record count before proceeding.

  5. Data import into Freshsales

    We import into Freshsales in record-dependency order: Accounts first, then Contacts with AccountId resolved, then Deals with OwnerId resolved by email match, then Cases, Activities, Leads, and Campaigns. Custom fields are created in Freshsales before the relevant record type import. Import throttling respects the Freshsales API rate limit for the destination plan tier using exponential backoff. Each phase emits a row-count reconciliation report confirming the destination count matches the source export count.

  6. Cutover, delta validation, and Workflow handoff

    We freeze Workbooks writes during the cutover window, run a final delta export of any records modified since the last full export, and import the delta into Freshsales. We enable Freshsales as the system of record and deliver the Workflow and Automation inventory document to the customer admin for rebuild in Freshsales Workflow Builder. We support a three-day hypercare window to resolve any reconciliation issues. Post-migration administration, training, and workflow rebuild are outside standard scope and require a separate engagement.

Platform deep dives

Context on both ends of the pair

Workbooks logo

Workbooks

Source

Strengths

  • Native quotation, order, and invoice handling eliminates the need for a separate CPQ or accounting tool on mid-market deals.
  • Lead aggregation and data enrichment features pull firmographic data automatically, reducing manual prospecting work.
  • Multilingual interface and multi-currency support accommodate UK and European teams without a costly upgrade.
  • Integrated case management with pipeline visibility gives support and sales a shared view of account health.
  • Sandbox environment available on all tiers for testing configuration changes before applying them to live data.

Weaknesses

  • Record save latency increases significantly as the database grows beyond ~50,000 active records.
  • UI and interaction patterns feel dated compared to newer CRM entrants, affecting user adoption among younger sales staff.
  • Sparse documentation and limited training resources create a steep learning curve for non-technical administrators.
  • The platform does not publish a public API reference for rate limits or bulk endpoints, making programmatic extraction harder to plan.
Freshsales logo

Freshsales

Destination

Strengths

  • Generous free tier for small teams with core CRM functionality without per-seat costs.
  • All-in-one sales CRM with built-in telephony, chat, and email reducing third-party tool dependency.
  • Freddy AI contact scoring and deal predictions available on Pro tier.
  • Multiple pipeline views with Kanban and list options across all plans.

Weaknesses

  • Reports lack depth compared to competitors like HubSpot, with limited customization options.
  • Integration setup is poorly documented with no clear guides for connecting third-party tools.
  • AI features gated behind $39/user/month Pro tier despite marketing emphasis on Freddy AI.
  • Bot sessions limited to 500 one-time allocation with no monthly refresh.

Complexity grading

How hard is this migration?

Standard CRM migration. 3 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 Workbooks and Freshsales.

  • Object compatibility

    B

    3 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

    C

    Workbooks: Workbooks imposes rate limits and result-set size caps. Excessive calls are throttled by being delayed or redirected via a delaying URL; clients are expected to follow these redirects as normal operation. Specific request-per-minute thresholds are not publicly published..

  • Data volume sensitivity

    A

    Workbooks exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Workbooks to Freshsales 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 Workbooks to Freshsales data migrations

Answers to the questions buyers ask most during Workbooks to Freshsales migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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

Book a free 30 minute consultation

Most Workbooks to Freshsales migrations land between three and five weeks for accounts with up to 15,000 Organisations, 25,000 People, and no Quotation or Invoice objects in scope. Migrations that include Business-tier Quotations and Invoices, large Case histories (over 10,000 open cases), extensive custom field sets, or complex parent-child relationships extend to seven to eleven weeks. The Freshsales migration itself typically takes one to two weeks of active data movement after scoping and setup are complete.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Workbooks.
Land in Freshsales, 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