Migrate from Perfect Books to Salesforce Sales Cloud

Perfect Books author contacts map directly to Salesforce Contacts. The contact's primary publisher (if applicable) becomes AccountId lookup. Pen name stored as a custom field; legal name maps to FirstName and LastName. Owner resolved by email match against Salesforce Users.

Perfect Books publisher and literary agency records map directly to Salesforce Accounts using the Account object. Account Name field maps to Name; website URL maps to Website; billing address details map to BillingAddress composite fields. Industry field defaults to 'Publishing' classification unless explicitly specified in source data, ensuring proper categorization in Salesforce reports and dashboards.

Perfect Books book deals transform into Salesforce Opportunities with custom fields for ISBN, format (print/ebook/audio), rights type (world English, translation, film), and royalty percentage. StageName maps from Perfect Books deal status: 'Active' → 'Negotiation', 'Signed' → 'Closed Won', 'Expired' → 'Closed Lost'.

Perfect Books royalty schedules require a custom object in Salesforce because standard Opportunities do not store multi-row royalty breakdowns. We create Royalty_Schedule__c with lookup to Opportunity, fields for Author_Contact__c, Royalty_Type__c, Royalty_Percentage__c, and Advance_Amount__c. This is the highest-complexity object in the migration.

Perfect Books tracks ISBN at the title level as free-form text. We create ISBN__c as a Text field on the Opportunity object in Salesforce. ISBN-13 values are stored as strings to preserve hyphenation patterns; during migration, a transformation step applies ISBN-13 format validation using regex rules. Post-migration, a Salesforce validation rule enforces the correct ISBN-13 pattern on all new entries.

Perfect Books activities logged against contacts map to Salesforce Tasks for calls and emails, and Events for scheduled meetings. Original activity timestamps and record owners are preserved throughout the migration. The Task WhatId field links to the related Opportunity or Account record, maintaining the relationship context within Salesforce for activity reporting.

Perfect Books file attachments including manuscripts, contracts, and cover art are re-uploaded to Salesforce Files. Files are linked to the parent record (Contact or Opportunity) via ContentDocumentLink. Salesforce default file size limit is 25MB per file; larger manuscripts exceeding this threshold are split into multiple files with a note referencing the complete set.

Perfect Books genre tags migrate to Genre__c as a multi-select picklist on the Opportunity object. We deduplicate source genre values from Perfect Books before applying Salesforce picklist value mapping. Any unmapped genre values from the source system are preserved as text in a secondary custom field to prevent data loss during the transition.

Format information (print, ebook, audiobook, translation) maps to Format__c picklist field on Opportunity. Each distinct format may generate a separate Opportunity record per rights agreement depending on your business rules. During migration planning, your team specifies the split rule to determine whether multi-format deals become single or multiple Opportunity records.

Perfect Books user accounts are matched to Salesforce Users by email address lookup. Unmatched owners are flagged in a pre-migration report for team review. Records without matched owners are assigned to a designated fallback owner or held pending Salesforce user provisioning. This ownership resolution step is completed before data loads to prevent ownership gaps in the target system.

Perfect Books notes migrate to Salesforce Notes rather than the legacy Note object. The body text content is preserved intact, and parent record links are maintained to ensure notes attach to the correct Contact, Account, or Opportunity. Rich-text formatting present in Perfect Books notes converts to plain text with line breaks preserved, ensuring readability in the target system.

If Perfect Books tracks foreign rights, subsidiary rights, or subsidiary rights separately, we create a Rights__c custom object with lookup to the parent Opportunity and fields for Territory__c, Language__c, Rights_Type__c, and Exclusivity__c. This is created only if source data contains rights-type fields.