Migrate from Perfect Books to Nutshell

Direct map. Perfect Books contacts map to Nutshell People. Primary company resolves via Perfect Books company_id → Nutshell account lookup. Multi-company contacts in Perfect Books collapse to the most-recently-modified primary company in Nutshell. All contact fields including name, email, phone, address, and custom fields transfer directly to the corresponding Nutshell Person record. Original Perfect Books contact IDs are preserved in a custom reference field for traceability and delta-run de-duplication. Owner assignments resolve by email match against Nutshell users.

Direct map. Perfect Books company records map 1:1 to Nutshell Company records. Company name, domain, industry, employee count, and annual revenue transfer directly. Parent-child company hierarchies in Perfect Books map to Nutshell's parent_company_id field. All company fields including billing address, shipping address, and custom fields transfer directly. Original Perfect Books company IDs are preserved in a custom reference field for traceability. Parent company relationships must resolve successfully — circular references are flagged for manual resolution before the migration completes.

Direct map. Perfect Books deals map to Nutshell Deals. Deal name, amount, close date, owner, and stage transfer directly. Perfect Books deal stage values map to Nutshell pipeline stage values via value-by-value mapping. Stage-entered timestamps preserved as custom datetime fields.

Direct map. Perfect Books pipelines map to Nutshell's single-pipeline model. If Perfect Books uses multiple pipelines, they merge into one Nutshell pipeline with stage prefixes or naming conventions to distinguish deal origins. Stage order and stage probability percentages transfer as part of the pipeline configuration. Teams using multiple pipelines in Perfect Books should review the merged stage structure before migration to ensure the resulting Nutshell pipeline reflects their sales process accurately. Stage prefix and naming decisions are documented in the migration plan for review.

Value mapping required. Each Perfect Books stage name maps to a corresponding Nutshell stage value. Stage probability percentages transfer as metadata where Perfect Books exposes them. Unmatched stage values require manual mapping before migration runs. FlitStack AI generates a stage mapping plan from the source data and presents it for confirmation. Teams with custom stage names or non-standard stage sequences should review the mapping carefully — stage order in Nutshell affects deal pipeline visualization and automation triggers. Approval of the stage mapping plan is required before migration commits.

Direct map. Perfect Books activities map to Nutshell's Activity timeline entries. Each activity retains its original subject, description, datetime, and owner. Activity type (call, email, meeting) maps to Nutshell's activity type field. Linked contacts and deals preserve their migration-assigned IDs.

Direct map. Perfect Books tasks map to Nutshell Tasks with title, description, due date, status, and owner transferred. Completed task flags map to Nutshell's completed status. Overdue calculations redo on import since Nutshell uses server-side date logic. Task priority levels transfer to Nutshell's priority field where available. Linked contacts and deals retain their migration-assigned IDs for proper association. Original Perfect Books task IDs are preserved in a custom reference field for traceability.

Direct map. Perfect Books notes map to Nutshell Activity records with type 'note'. Original note body and create datetime transfer. Notes linked to contacts or deals inherit the migration-assigned record IDs for proper association. Note attachments download during the export phase and re-upload to Nutshell as file attachments on the corresponding Activity record. Teams using notes for deal context should verify that note-to-deal associations are complete after migration, as Perfect Books may have notes without explicit deal links that require manual review.

Custom fields on Perfect Books objects require Nutshell custom field creation before migration. Text, number, date, currency, and dropdown field types map to equivalent Nutshell custom field types. Pick-list values in Perfect Books custom dropdowns require value mapping if Nutshell's existing options differ.

Owner resolution by email match. Perfect Books owner_id resolves against Nutshell users by email address. Unmatched owners are flagged before migration; records assign to a designated fallback Nutshell user. Owner change history does not transfer — final owner assignment at migration time applies.

Perfect Books file attachments linked to contacts, companies, or deals re-upload to Nutshell. File size limits apply (Nutshell's attachment size cap). Inline images in notes or descriptions download and rehost as attachments. Download URLs in Perfect Books may expire — file preservation begins during the export phase.

If Perfect Books maintains separate Lead records (distinct from Contact), they map to Nutshell Leads. Lead-specific fields (lead source, lead status, qualification notes) transfer to Nutshell Lead fields. Leads without a Nutshell equivalent remain as custom fields for reference. FlitStack AI validates lead-to-contact deduplication before migration — duplicate detection flags contacts and leads sharing the same email address for review. Lead assignment rules from Perfect Books do not transfer and must be recreated in Nutshell's lead routing settings.