Migrate your Workbooks data
UK-origin mid-market CRM with native quote-to-order and invoice handling, built for 20–50 person professional services teams who need more than sales-only CRMs can offer.
In its favor
Why people choose Workbooks
The signal that keeps Workbooks on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Quote-to-order workflow is built in, not bolted on—organisations with complex sales cycles pick Workbooks to avoid juggling a separate quoting tool alongside their CRM.
Integrated invoicing and purchase order handling on the Business tier means finance and sales share the same record without manual re-entry across systems.
Lead aggregation and augmentation features pull enrichment data automatically, reducing manual research time for B2B sales teams with limited SDR capacity.
Integrations with Mailchimp, Microsoft Outlook, and accounting packages keep email and financial data consistent across platforms without custom middleware.
The multilingual interface and multiple currency support make it viable for UK and European teams operating across borders without switching to a global-tier CRM.
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.
Reasons to switch
Why people leave Workbooks
The recurring reasons buyers give for replacing Workbooks. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Workbooks fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Workbooks pricing overview
Workbooks prices per user per month across five tiers, ranging from a 30-day free trial through Business Pro at custom pricing. The CRM tier at $47 PUPM covers core sales functionality; the Business tier at $97 PUPM adds native invoicing and order management. Published pricing varies slightly between the official website and third-party aggregator pages.
Free Trial
Tier 1 of 5
$0 /per user, per month (30 days)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Workbooks's schedule — see our quote-based pricing →
What gets migrated
Workbooks object support
Object-by-object support for Workbooks migrations. Per-pair details surface during scoping.
Organisations
Fully supportedOrganisations are Workbooks' company/account object. We extract all standard fields (name, address, industry, classification) plus custom fields defined on the Organisation record type. iFrame custom fields store only a URL reference and are exported as-is; file-upload fields are downloaded separately and linked by filename.
People
Fully supportedPeople records hold individual contacts linked to an Organisation via the 'Organisation' lookup field. We preserve the link during migration and map People to Contacts, Leads, or Person objects in the destination CRM depending on its data model.
Opportunities
Fully supportedOpportunities in Workbooks represent deals in a pipeline with stage, probability, and value. We extract all stage history, owner assignment, and expected close date. Probabilities are preserved as a custom numeric field if the destination does not support native stage-level probability.
Cases
Fully supportedCases are Workbooks' ticketing and issue-tracking object. We extract case status, priority, assigned user, related Organisation, description, and all case activities. Open cases and resolved cases are migrated with their full history intact.
Quotations
Mapping requiredQuotations contain a header (related Organisation, owner, validity date) and line items (product, quantity, price, discount). We map line items to destination quote-line or opportunity product records. Custom pricing rules and discount structures require explicit field mapping because they vary by deployment.
Invoices
Mapping requiredInvoices are available on the Business tier and above. We extract invoice header data, line items, payment status, and credit note associations. Attachments stored against invoices are downloaded and re-attached at the destination.
Sales Orders / Purchase Orders
Mapping requiredOrders are tied to an Organisation and quotation. We extract order headers, line items, and status. Order-to-invoice linkage is preserved as a reference note if the destination does not support native order chaining.
Activities
Fully supportedActivities represent logged calls, emails, meetings, and tasks linked to an Organisation or Person. We extract activity type, date, duration, subject, description, and owner. Activity history is bulk-exported to preserve the engagement timeline.
Campaigns
Mapping requiredCampaigns track marketing initiatives and their associated leads. We extract campaign name, status, start/end dates, and associated lead and person memberships. Campaign response data is migrated as campaign member records or notes depending on destination schema.
Leads
Mapping requiredWorkbooks Lead records hold pre-conversion prospect data. We extract lead source, status, rating, and assigned owner. Leads are mapped to the destination Lead or Contact object; the original Lead status is stored as a custom property in the destination.
Custom Fields
Mapping requiredWorkbooks supports custom fields of types text, number, date, dropdown, checkbox, file upload, and iFrame. We map each custom field by name and type. File-upload fields require separate binary extraction; iFrame fields export as URL strings only.
Contracts
Mapping requiredContract records on the CRM or Business tier hold agreement details, related Organisation, start/end dates, and renewal terms. We extract contract metadata and any attached documents. Renewal reminders and SLA terms are not migratable and must be rebuilt at the destination.
| Object | Support | Notes |
|---|---|---|
| Organisations | Fully supported | Organisations are Workbooks' company/account object. We extract all standard fields (name, address, industry, classification) plus custom fields defined on the Organisation record type. iFrame custom fields store only a URL reference and are exported as-is; file-upload fields are downloaded separately and linked by filename. |
| People | Fully supported | People records hold individual contacts linked to an Organisation via the 'Organisation' lookup field. We preserve the link during migration and map People to Contacts, Leads, or Person objects in the destination CRM depending on its data model. |
| Opportunities | Fully supported | Opportunities in Workbooks represent deals in a pipeline with stage, probability, and value. We extract all stage history, owner assignment, and expected close date. Probabilities are preserved as a custom numeric field if the destination does not support native stage-level probability. |
| Cases | Fully supported | Cases are Workbooks' ticketing and issue-tracking object. We extract case status, priority, assigned user, related Organisation, description, and all case activities. Open cases and resolved cases are migrated with their full history intact. |
| Quotations | Mapping required | Quotations contain a header (related Organisation, owner, validity date) and line items (product, quantity, price, discount). We map line items to destination quote-line or opportunity product records. Custom pricing rules and discount structures require explicit field mapping because they vary by deployment. |
| Invoices | Mapping required | Invoices are available on the Business tier and above. We extract invoice header data, line items, payment status, and credit note associations. Attachments stored against invoices are downloaded and re-attached at the destination. |
| Sales Orders / Purchase Orders | Mapping required | Orders are tied to an Organisation and quotation. We extract order headers, line items, and status. Order-to-invoice linkage is preserved as a reference note if the destination does not support native order chaining. |
| Activities | Fully supported | Activities represent logged calls, emails, meetings, and tasks linked to an Organisation or Person. We extract activity type, date, duration, subject, description, and owner. Activity history is bulk-exported to preserve the engagement timeline. |
| Campaigns | Mapping required | Campaigns track marketing initiatives and their associated leads. We extract campaign name, status, start/end dates, and associated lead and person memberships. Campaign response data is migrated as campaign member records or notes depending on destination schema. |
| Leads | Mapping required | Workbooks Lead records hold pre-conversion prospect data. We extract lead source, status, rating, and assigned owner. Leads are mapped to the destination Lead or Contact object; the original Lead status is stored as a custom property in the destination. |
| Custom Fields | Mapping required | Workbooks supports custom fields of types text, number, date, dropdown, checkbox, file upload, and iFrame. We map each custom field by name and type. File-upload fields require separate binary extraction; iFrame fields export as URL strings only. |
| Contracts | Mapping required | Contract records on the CRM or Business tier hold agreement details, related Organisation, start/end dates, and renewal terms. We extract contract metadata and any attached documents. Renewal reminders and SLA terms are not migratable and must be rebuilt at the destination. |
Gotchas
What to watch for in Workbooks migrations
Issues we've hit on past Workbooks migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving Workbooks?
Where Workbooks customers move next
12 destinations Workbooks can migrate to.
How a Workbooks migration works
Four steps, Workbooks-specific
Connect
API key with mandatory expiration date and at least one permitted IP address. Keys are created at Start > Configuration > Automation > API Keys and operate under the capabilities and permissions of a designated 'Access as User'. Deleting or disabling that user revokes API access. into Workbooks. Scopes limited to read-only on the data we move.
Map
We translate Workbooks-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Workbooks quirks before production.
Migrate
Full migration with Workbooks rate-limit handling. Rollback available throughout.
FAQ
Workbooks migration FAQ
Answers to the questions buyers ask most during Workbooks migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Workbooks migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Workbooks.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Workbooks setup and destination — written quote back within a business day.