CRM migration
Field-level mapping, validation, and rollback between Workbooks and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Workbooks
Source
Freshsales
Destination
Compatibility
9 of 10
objects map 1:1 between Workbooks and Freshsales.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
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 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
Freshsales
Account
1:1Workbooks 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
Freshsales
Contact
1:1Workbooks 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
Freshsales
Deal
1:1Workbooks 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
Freshsales
Case
1:1Workbooks 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
Freshsales
Deal Line Item or Note
1:1Quotations 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
Freshsales
Note or Custom Field
1:1Invoices 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)
Freshsales
Activity (Task, Event)
1:1Workbooks 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
Freshsales
Custom Fields
lossyWorkbooks 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
Freshsales
Lead
1:1Workbooks 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
Freshsales
Campaign
1:1Workbooks 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.
| Workbooks | Freshsales | Compatibility | |
|---|---|---|---|
| Organisation | Account1:1 | Fully supported | |
| Person | Contact1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Case | Case1:1 | Fully supported | |
| Quotation | Deal Line Item or Note1:1 | Fully supported | |
| Invoice | Note or Custom Field1:1 | Fully supported | |
| Activity (Call, Email, Meeting, Task) | Activity (Task, Event)1:1 | Fully supported | |
| Custom Fields | Custom Fieldslossy | Mapping required | |
| Lead | Lead1:1 | Fully supported | |
| Campaign | Campaign1:1 | 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.
Workbooks gotchas
Record save latency on large datasets
Custom Fields require manual field-level mapping
Quotation and Invoice exports require Business tier
iFrame custom fields export as URL strings only
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Workbooks
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Workbooks and Freshsales.
Object compatibility
3 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
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
Workbooks exposes a bulk API — large-volume migrations stream efficiently.
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 Workbooks to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Workbooks to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Workbooks
Other ways to arrive at Freshsales
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.