Migrate from Workbooks to Salesforce Sales Cloud

Workbooks Organisation records map to Salesforce Account. Organisation name becomes Account Name, address fields map to BillingAddress, industry classification maps to Industry, and any custom fields defined on Organisation map to equivalent custom Account fields. We use Organisation name and domain as a dedupe key during Account insert to prevent duplicate accounts from repeated exports. Account is the parent record; it must exist before any Contact import so that AccountId lookup is satisfied on insert.

Workbooks Person records map to Salesforce Contact. The Organisation lookup field on Person resolves to the AccountId on the Contact during migration, preserving the company-contact link. Person name fields (first name, last name, title, phone, email) map to their Salesforce Contact equivalents. If the Person has no linked Organisation, the Contact is created without an AccountId and placed in a reconciliation queue for the customer's admin to assign after migration.

Workbooks Lead records hold pre-conversion prospect data with lead source, status, rating, and owner. We evaluate each Lead against the customer's criteria: Leads with clear buyer intent or existing Opportunity association map to Salesforce Contact attached to the relevant Account; unqualified Leads remain as Salesforce Lead records with lead source and rating preserved in custom fields. The split rule is defined during scoping based on the customer's Workbooks pipeline configuration. Original Workbooks Lead status is preserved in a custom field wb_original_lead_status__c on the destination record.

Workbooks Opportunities map to Salesforce Opportunity. Stage, probability, value, expected close date, owner, and related Organisation all migrate. We resolve the Organisation-to-AccountId reference during the Opportunity phase (Accounts must load first). Closed-Won and Closed-Lost reason fields from Workbooks custom properties map to Salesforce Loss Reason and Win Reason custom fields. Opportunity is the child of Account; AccountId must be resolved before Opportunity insert.

Workbooks pipeline stages map to Salesforce Stage values on the Opportunity object. We pre-create a Sales Process in Salesforce that whitelists the relevant stage values for each Workbooks pipeline, and assign a Record Type per pipeline to scope page layouts and stage sets to specific lines of business. Stage probability percentages migrate from Workbooks to Salesforce StageProbability, rounded to the nearest integer allowed by Salesforce.

Workbooks Cases map to Salesforce Case if the destination Salesforce org includes Service Cloud or if the customer adds Service Cloud during migration. Case status, priority, description, assigned user, and related Organisation map to their Salesforce equivalents. Open cases and resolved cases both migrate; status mapping is configured during scoping against the customer's Workbooks case status values. Case activities (comments and internal notes) migrate as CaseComment records.

Workbooks Quotations are only available on the CRM and CRM Pro tiers and above (Business tier required for full quoting). We verify the source subscription tier before including Quotations in the migration scope. Quotation headers (related Organisation, owner, validity date) map to Salesforce Quote fields. Line items (product, quantity, unit price, discount) map to QuoteLineItem records linked to the Quote. If the destination Salesforce org does not have Quotes enabled, quotation data migrates as Opportunity Product records instead.

Workbooks Invoices are available only on the Business and Business Pro tiers. If the source subscription is on CRM or CRM Pro, Invoices do not exist in the export and are flagged as out-of-scope during scoping. When available, invoice headers, line items, payment status, and related Organisation map to Salesforce Asset records or a custom Invoice__c object depending on whether the destination org uses Salesforce Financial Services Cloud or a custom invoice schema.

Workbooks Sales Orders and Purchase Orders map to Salesforce Order records. Orders are tied to an Organisation and quotation. We extract order headers, line items, and status. If the destination Salesforce org does not have the Order object enabled, order data migrates as custom Order__c records with a note flagging the gap for the customer's admin. Order-to-invoice linkage is preserved as a reference field on the record.

Workbooks Activities represent logged calls, emails, meetings, and tasks linked to an Organisation or Person. We map call activities to Task with TaskSubtype=Call and CallDurationInSeconds in a custom field. Meeting activities map to Event with StartDateTime, EndDateTime, and Location preserved. Email activities map to Salesforce EmailMessage records linked to a Task for the activity timeline. All Activity records carry the original Workbooks timestamp to preserve timeline ordering. We use the Salesforce Bulk API 2.0 for large activity histories to avoid the silent record drops that CSV loaders produce at volume.

Workbooks Campaigns track marketing initiatives and associated leads. We extract campaign name, status, start and end dates, and associated lead memberships. Campaign Member data migrates as CampaignMember records linked to the relevant Salesforce Leads or Contacts. Campaign response data migrates as custom fields on Campaign to preserve historical response metrics without rebuilding the reporting model.

Workbooks custom fields on Organisation, Person, Opportunity, Case, Quotation, Invoice, and Order objects map to Salesforce custom fields. Workbooks deployments vary significantly in which custom fields exist and what they are called; there is no unified schema export listing all custom fields across record types. We request read-only access to the source Workbooks account and enumerate custom fields per record type before writing the migration spec. Dropdown fields in Workbooks map to Salesforce picklist fields with the relevant values pre-populated in the destination schema.

File upload fields in Workbooks store attachments against a record. Binary files (PDFs, images, documents) are downloaded separately from the Workbooks export and re-attached to the destination record in Salesforce via the ContentDocumentLink object. We preserve the original file name and upload date. The customer confirms whether attachments are in scope during scoping, as large binary sets add extraction and upload time to the project.

Workbooks Contract records hold agreement details, related Organisation, start and end dates, and renewal terms on the CRM or Business tier. We extract contract metadata and any attached documents. Renewal reminder configuration is not a data field and does not migrate; we document the renewal terms and renewal reminder settings so the customer's Salesforce admin can configure Salesforce Contracts or a custom renewal reminder flow post-migration.

Workbooks Owners referenced on Organisation, Person, Opportunity, Case, Quotation, and Activity records map to Salesforce User by email address. We extract all distinct Owner references, match against the destination org's User table, and hold any unmatched owners in a reconciliation queue. The customer's Salesforce admin provisions missing Users before production migration begins, because OwnerId is a required reference on most standard objects.