Migrate from Perfect Books to HubSpot

Direct map. HubSpot Contact properties receive the mapped fields from Perfect Books. Each contact in Perfect Books creates one HubSpot Contact. If Perfect Books stores multiple email addresses or phone numbers on a single contact, secondary values are appended as a custom property in HubSpot.

Direct map. Perfect Books companies map to HubSpot Companies. HubSpot's parent-company field receives the Perfect Books parent-company association if hierarchical company structures exist. Multi-company relationships for a single contact collapse to HubSpot's primary-company association with secondary associations created via the HubSpot associations API.

Direct map. Perfect Books deals map to HubSpot Deals with the deal name, amount, close date, owner, and pipeline stage. The Perfect Books deal pipeline maps to a HubSpot deal pipeline — each Perfect Books pipeline creates one HubSpot pipeline with matching or equivalent stage labels.

HubSpot pipelines and stages are created based on Perfect Books pipeline configuration. Stage names transfer value-by-value; stage probability and forecast category are applied per HubSpot pipeline settings. If Perfect Books stages have no HubSpot equivalent, new stages are created and flagged for your team to configure.

Perfect Books owner fields resolve to HubSpot OwnerId by email match against HubSpot users. Unmatched owners are flagged before migration — your team can invite them to HubSpot first or assign records to a fallback owner. No record migrates without a resolved owner.

Perfect Books call logs map to HubSpot Call engagements. Original call timestamp, duration, owner email, and the parent contact or deal association are preserved. Call outcome or disposition maps to a HubSpot custom property if it exists in Perfect Books.

Email history in Perfect Books becomes HubSpot Email engagements. Subject line, timestamp, owner, and association to the originating contact or deal transfer. If Perfect Books stores email body content, it is saved as a HubSpot engagement note or note attachment.

Perfect Books meetings map to HubSpot Meeting engagements with start time, end time, owner, and linked contact or deal preserved. Notes in Perfect Books become HubSpot Notes attached to the relevant Contact, Company, or Deal record. The association between notes and their parent records is maintained using HubSpot's engagement association API, ensuring that the context of each note remains linked to the originating record after migration.

Perfect Books custom objects migrate as HubSpot custom objects only on Enterprise plans. Your team must register the custom object schema with HubSpot before migration — FlitStack delivers a schema setup plan specifying the object name, primary property, and association labels required. Many-to-many relationships between custom objects need HubSpot junction objects.

File attachments in Perfect Books are downloaded and re-uploaded to HubSpot Files, attached to the relevant Contact, Company, or Deal record. HubSpot file size limits apply (default 25MB per file). Inline images embedded in notes are extracted and rehosted individually.

Any Perfect Books custom fields that have no HubSpot standard property equivalent are created as HubSpot custom properties. HubSpot property names use lowercase with hyphens removed and spaces replaced by underscores. Pick-list fields in Perfect Books map to HubSpot option-based properties with the original values preserved as options.