Migrate from Perfect Books to HighLevel

Direct map to HighLevel Contact. HighLevel requires a primary CompanyId for each contact — contacts without a company assignment receive a default 'Unassigned' company record. Email address serves as the unique identifier for deduplication and owner matching. Any duplicate contacts detected by email are flagged for review before final import.

Direct map to HighLevel Company. Company hierarchies (parent/child) in Perfect Books map to the Parent Company field in HighLevel. Multi-contact associations collapse to the primary contact role on the company record. If multiple contacts share the same company name, the system uses domain matching to consolidate them under a single company entry.

Perfect Books deals map to HighLevel Opportunities. Pipeline stages in Perfect Books map to Opportunity stages in the target HighLevel pipeline. Stage names require value-by-value mapping when the pick-list values differ between platforms. Any mismatched stage names are documented in the field mapping sheet for manual adjustment before the migration run.

Each Perfect Books deal pipeline maps to a corresponding HighLevel Pipeline. Pipelines define the stage pick-list values, probability weights, and forecast categories for opportunities within that pipeline. HighLevel supports multiple pipelines per sub-account. During migration, we replicate the stage order and any custom probability settings to preserve forecasting accuracy.

Direct map to HighLevel Task. Original due dates, assigned owners, and task status (completed/pending) are preserved. Tasks linked to contacts or opportunities retain their parent-record association in HighLevel. If a linked contact or opportunity does not exist in HighLevel, the task is flagged for manual re-association after migration.

Direct map to HighLevel Note. Notes attached to contacts, companies, or opportunities preserve their parent-record link. Rich-text formatting is converted to HighLevel's note body format; inline images are downloaded and re-uploaded to HighLevel's file storage. Any unsupported formatting, such as embedded macros, is stripped and noted for manual review.

Perfect Books calendar appointments map to HighLevel Appointments. Original start/end times, location, assigned user, and linked contact/company are preserved. Recurring appointment series are expanded to individual HighLevel appointment records. If a linked contact or company is missing in HighLevel, the appointment is temporarily assigned to a placeholder and flagged for correction.

Tags in Perfect Books map directly to Tags in HighLevel. Tags are preserved as reference data for segmentation — note that HighLevel workflows can read and write tags, but the tag logic encoded in Perfect Books sequences requires manual rebuild in HighLevel's workflow builder.

Perfect Books custom fields on contacts create corresponding custom fields in HighLevel. Field type mapping: text → text, number → number, date → date, picklist → picklist. Custom field names are preserved as field labels; API names are auto-generated per HighLevel conventions.

Perfect Books custom fields on contacts create corresponding custom fields in HighLevel. Field type mapping: text → text, number → number, date → date, picklist → picklist. Custom field names are preserved as field labels; API names are auto-generated per HighLevel conventions. We also verify that the custom field is visible in the target contact layout before loading data.

Company-level custom fields in Perfect Books map to custom fields on the HighLevel Company object. The same type-mapping rules apply as for contact custom fields. Fields are created in the target HighLevel sub-account before migration data loads. We also ensure the field appears in the appropriate Company layout and is accessible to users with the correct role.

Deal-level custom fields in Perfect Books map to custom fields on the HighLevel Opportunity object. Probability overrides, custom stage metadata, and deal-specific properties are preserved. Field creation order must precede opportunity migration to satisfy the schema. We also validate that the custom fields are correctly linked to the pipeline stages before data load.

File attachments in Perfect Books are downloaded and re-uploaded to HighLevel Files. File associations with contacts, companies, or opportunities are preserved. HighLevel's file size limits (25MB default) apply; files exceeding the limit are flagged for manual handling.

Workflows, sequences, and automation rules in Perfect Books do not migrate. They require manual rebuild in HighLevel's workflow builder. FlitStack AI exports the workflow definitions as a reference document to assist the rebuild process. This reference includes step-by-step logic, trigger conditions, and any associated time delays for reconstruction.