Migrate from Perfect Books to Pipedrive

Perfect Books Contacts map directly to Pipedrive People. The Person object stores name, email, phone, job title, and address fields. A primary Organization link is required in Pipedrive — contacts without a company in Perfect Books get attached to a default placeholder Organization record.

Perfect Books Companies map to Pipedrive Organizations. The Organization object stores name, domain/website, industry, employee count, address, and custom fields. We create Organizations in Pipedrive before importing any Person records so the org_id lookup resolves correctly during Person migration. Parent-child company hierarchies in Perfect Books map to Organization.ParentId if that relationship exists in the source schema, preserving any nested company structures in the destination.

Perfect Books Deals map to Pipedrive Deals — the closest 1:1 object pair. Each Deal carries a title, value, pipeline reference, stage name, expected close date, owner, and linked Person and Organization. Pipeline and stage values require value-by-value mapping since Perfect Books pipeline names differ from Pipedrive's pipeline configuration.

Perfect Books deal pipelines map to Pipedrive Pipelines — each pipeline is a distinct swim-lane configuration in Pipedrive. We create matching Pipelines in Pipedrive before importing Deals so stage values resolve correctly against the correct pipeline's stage pick-list. This pre-creation step is mandatory because Pipedrive's import API requires pipeline_id and stage_id references to exist before Deals can be associated with them.

Each pipeline stage in Perfect Books maps to a named Stage within the corresponding Pipedrive Pipeline. Stage names are mapped value-by-value, preserving the sequence and order of stages as they appear in Perfect Books. Probability and forecast-category values are applied from Pipedrive's defaults unless custom values are specified in the migration plan, in which case we configure the stage with the requested probability at creation time.

Email records in Perfect Books migrate as Pipedrive Activities with type='email'. Original timestamps, subject, body, and associated Person or Deal link are preserved. Note: Pipedrive exports emails from active users only — shared email configuration in Perfect Books is verified before extraction.

Call logs in Perfect Books migrate as Pipedrive Activities with type='call'. Duration, outcome, and original timestamps transfer. Call recordings do not export from Pipedrive's API — if recordings exist in Perfect Books, they must be downloaded separately and re-hosted in Pipedrive's file storage.

Meeting records in Perfect Books migrate as Pipedrive Activities with type='meeting'. Start time, end time, location, attendees, and notes are preserved during the import. If meetings have multiple attendees, we create linked Person records and reference them in the activity attendee list. Pipedrive calendar integration can be re-established post-migration to sync future meetings natively with Google Calendar or Outlook.

Notes in Perfect Books migrate as Pipedrive Activities with type='note'. Rich-text formatting is preserved where supported. If notes contain inline images, those assets are downloaded and re-uploaded to Pipedrive's file storage, and the note body is updated with the new file URLs.

File attachments associated with Contacts, Companies, or Deals in Perfect Books are downloaded and re-uploaded to Pipedrive's file storage, then linked to the corresponding Person, Organization, or Deal record. File size limits in Pipedrive apply — files over 25MB require alternative hosting with a link stored in the record.

If Perfect Books contains custom objects beyond Contacts, Companies, and Deals, we map them to Pipedrive custom fields on the closest standard object (Person, Organization, or Deal). Pipedrive does not support independent custom objects — all custom data attaches to a parent standard object.

Perfect Books users are matched to Pipedrive users by email address. Unmatched owners are flagged before migration — teams either invite the user to Pipedrive first or assign their records to a fallback user. No record imports without a resolved Pipedrive owner.