Migrate from Checkbox to HighLevel

Every Checkbox contact record maps to a HighLevel Contact. Primary fields (name, email, phone) migrate directly. Custom properties on the Checkbox record map to HighLevel custom fields on the Contact object. Owner resolution happens by email match against HighLevel user accounts.

If the Checkbox intake form captures company name, it lands as a Company record in HighLevel. Contacts without a company association create an unassigned placeholder company or link to a default 'No Company' record at your direction. Company-city, state, and domain fields map to HighLevel's standard company address and website fields.

Checkbox does not have a native deal object. Deal amounts, stage names, and close dates stored in Checkbox custom property fields map into HighLevel Opportunities. We create a single pipeline in HighLevel unless your Checkbox setup uses multiple deal-type properties, in which case each distinct deal type becomes its own HighLevel pipeline.

Tags are flat string labels in both platforms. Every Checkbox tag attached to a contact migrates to the same tag on the HighLevel Contact. Multi-tag records generate multiple tag assignments on the destination side. Tags with identical names are deduplicated — no duplicate tag records created.

Each Checkbox custom property becomes a HighLevel custom field on the Contact object (or on Opportunity if the property relates to deal data). Field types map by inferred type: text properties become text fields, date properties become date fields, numeric values become number fields. Pick-list properties from Checkbox become choice-type custom fields in HighLevel.

Checkbox intake forms do not have a direct equivalent in HighLevel for purposes of data preservation — the form structure and conditional logic must be rebuilt in HighLevel's Form Builder. We export the form schema and field list as a rebuild reference. Form submission events migrate as notes on the contact record with a reference to the source form.

Checkbox records each form submission with a timestamp and submission ID. These migrate as Notes on the HighLevel Contact with the submission timestamp and a reference link back to the source record. This preserves the engagement context without requiring a custom activity object.

Checkbox conditional logic — skip-to-question rules, conditional show/hide, branching paths — does not have a HighLevel equivalent that accepts exported rules. We document every conditional branch as a text export so your HighLevel admin can rebuild the logic in the Workflow Builder or Form Builder. No automation logic migrates automatically.

Checkbox records an assigned user or owner per record. We resolve each Checkbox owner by email against HighLevel user accounts. Unmatched owners are flagged before migration — either the HighLevel account needs to invite the user first or their records are reassigned to a fallback owner designated by your team.

Checkbox file attachments linked to contact records are downloaded and re-uploaded to HighLevel's file storage, then attached to the corresponding contact record. File size limits apply (HighLevel's upload limits per plan). Inline images embedded in notes are re-hosted as HighLevel-hosted files.