Migrate from Perfect Books to Twenty CRM

Perfect Books contacts (authors, editors, buyers) map directly to Twenty's People object. Email is the unique identifier for People imports. Each contact must have a workspace member matched by email if you want to assign owner records in Twenty. During extraction, FlitStack de-duplicates contacts by email and flags any duplicates for review before final import.

Perfect Books author-specific fields like royalty_rate and contract_type have no native Twenty equivalent. These migrate as custom fields on People — created in Settings → Data Model before import. Select-type fields (contract_type) map to Twenty's select field type with the same pick-list values preserved.

Perfect Books publishing houses and imprints map to Twenty's Company object. The imprint name maps to Company.name. For multi-imprint publishers with parent-child relationships, Perfect Books' parent_imprint_id maps to Twenty's Company.parentId — the parent company must be imported first per Twenty's import order rules.

Publisher website domain from Perfect Books maps to Company.website in Twenty. Publisher industry classification maps to the industry select field using value mapping where Perfect Books taxonomy differs from Twenty's default pick-list. If an industry value does not match any Twenty pick-list option, FlitStack maps it to the 'Other' option and records the original value in a custom field for later review and adjustment.

Perfect Books deal records (book deals, rights agreements, royalty contracts) map to Twenty Opportunities. The publishing lifecycle stage (Proposal, Under Review, Contracted, Published, Rights Sold) maps to Twenty pipeline stages — value mapping applied per stage name. Deal monetary value (advance, royalty percentage) maps to Opportunity.amount; closeDate maps from expected_publication_date or contract_expiry_date.

Each Perfect Books deal stage maps to a specific Twenty pipeline stage via value-by-value mapping. Stage names that don't have an exact Twenty equivalent (e.g., 'Rights Review', 'Contract Negotiation') are mapped to the closest stage and flagged for admin confirmation before migration commits.

If Perfect Books stores book as a separate entity related to deals, a Book custom object is created in Twenty with fields: title (text), isbn (text), format (select: hardcover/paperback/ebook/audio), publication_date (date). The Opportunity is linked to the Book custom object via a relation field. For simpler setups, these fields are added as custom fields on Opportunity.

Perfect Books annotations and editorial notes migrate as Twenty Notes. The note body maps to Note.body, the linked contact or publisher maps to Note.targetObject (Twenty supports attaching Notes to People, Companies, and Opportunities). Original timestamps are preserved as Note.createdAt. All notes are validated for length and stripped of any unsupported formatting before insertion to prevent import errors.

Perfect Books tasks (follow-up reminders, manuscript review tasks, royalty payment reminders) map to Twenty Tasks. Task.dueDate maps from the source due date. Assignee is resolved by email match to a Twenty workspace member. Completed status maps to Task.completedAt. If a due date falls in the past, FlitStack flags the task for manual review and can optionally set it to the current date to avoid overdue anomalies.

Perfect Books allows an author (contact) to be associated with multiple publishers simultaneously. Twenty supports a single primary company per contact via companyId. The primary publisher (most recent or highest-value contract) is assigned as companyId; additional publisher associations are preserved as a custom relation field or custom object (AuthorPublishers) if the team needs full N:N visibility.

Any Perfect Books custom fields tracking publishing-specific metadata (territory rights, translation rights, print run size, discount schedule) require pre-creation in Twenty's Data Model. Field type is matched (text, number, date, select) and pick-list values are carried over verbatim. We flag any field that uses a data type not natively supported by Twenty (e.g., complex formula fields) for admin decision before migration.

Perfect Books may store contract PDFs, manuscript files, and cover images as attachments. Twenty's cloud version does not have a native attachment storage system equivalent to Salesforce Files. We migrate file attachment URLs as a custom URL field on the related record (Contact or Opportunity) and advise teams to host files in a separate document store (S3, Google Drive) post-migration.