Migrate from Perfect Books to Microsoft Dynamics 365 Sales

Direct map. Dynamics 365 Contact requires an AccountId lookup — records without a primary company in Perfect Books land under a default 'Unassigned Account' record or are flagged for owner resolution before migration commits, including handling of duplicate records and ensuring referential integrity across all linked entities.

Direct map if Perfect Books maintains a separate Lead entity. Leads in Dynamics 365 have a dedicated Status pick-list and a separate conversion flow that creates an Account and Contact upon qualification — we preserve the original lead source and status value during migration.

Direct map. Perfect Books company records map to Dynamics 365 Account. Parent-child company hierarchies in Perfect Books translate to the ParentAccountId lookup in Dynamics 365. The parent account must migrate first to resolve circular references. This also preserves the hierarchical context for reporting and segmentation purposes.

Direct map. Perfect Books deals become Dynamics 365 Opportunities. The deal name maps to Opportunity.Name, and close date maps to ActualCloseDate once the deal is won, or EstimatedCloseDate while open. We preserve the original Perfect Books deal ID for reconciliation.

Perfect Books pipeline structures — typically a flat list of stages — map to Dynamics 365 Business Process Flows. Each Perfect Books pipeline becomes one BPF in Dynamics 365. The BPF stage names are mapped value-by-value from the source stage labels.

Stage names require explicit value-by-value mapping because Dynamics 365 stages are scoped per Business Process Flow. Probability and forecast category are reapplied based on Dynamics 365 stage defaults. Stage-entered timestamps from Perfect Books are preserved in custom datetime fields to maintain historical accuracy.

Perfect Books custom objects map 1:1 to Dynamics 365 custom tables on Dataverse. Custom table relationships in Perfect Books that use N:N linking require junction tables in Dynamics 365 — we surface this as a pre-migration design decision for future extensibility and reporting.

Phone calls and emails map to Dynamics 365 Task records with Type='phonecall' or 'email'. Meetings map to Event records with original start/end times and duration preserved. Parent record links (regarding) map to the RegardingObjectId lookup in Dynamics 365, ensuring continuous activity tracking across the CRM.

Perfect Books notes migrate as Dynamics 365 Annotations. We detect rich-text formatting and convert HTML note bodies to the Annotation entity's notetext field. Inline images in notes are downloaded, rehosted in SharePoint, and replaced with file links in Dynamics 365.

File attachments on records re-upload to SharePoint document libraries attached to the corresponding Dynamics 365 record. File size limits apply: Dynamics 365 default caps individual uploads at 32MB; files larger than this are chunked and re-assembled in SharePoint, to support compliance and audit requirements.

Every Perfect Books custom field requires a corresponding new_customfield field in Dynamics 365. Field data type mapping follows Dataverse conventions: text fields become nvarchar, numbers become integer or decimal, dates become datetimeoffset. We create all custom fields in Dynamics 365 before the migration run.

Perfect Books owner records resolve to Dynamics 365 SystemUser by email address match. Unmatched owners are flagged with a migration warning — you either invite them to Dynamics 365 before migration or assign their records to a fallback owner. No record lands without a valid OwnerId.