Migrate your Camp Automation data

Contacts are the primary CRM object in Camp Automation's data model. We map standard Contact properties (name, email, phone, company association) directly to the destination CRM's Contact or Person object. No known schema quirks at this time.

Company/Account records are standard CRM objects. We preserve the company name, domain, industry, and size fields. Where the destination uses a flat Contact model without a separate Company object, we merge company fields into the Contact record.

Deal records in Camp Automation include pipeline, stage, value, and close date. We map pipeline stages using a named stage-to-stage mapping since stage naming conventions differ across CRMs. Custom Deal properties are handled as custom field mappings.

Campaigns are multi-channel objects that group email, SMS, social, and push notification activities. We import campaign records as a single parent object and attach channel-specific child records (email sends, SMS messages) to preserve the campaign hierarchy in the destination.

Email templates include subject line, HTML body, and variable placeholders. We export templates as HTML with inline CSS and preserve variable syntax. Where the destination uses a different template language (e.g., Handlebars vs Liquid), we adapt the variable syntax at migration time.

Automation workflows consist of trigger conditions and action sequences. Migration requires mapping each trigger type (form submission, email open, deal stage change) to an equivalent in the destination platform. Complex multi-branch logic may need manual reconstruction in the destination.

Custom fields on Contacts, Companies, and Deals are discovered via schema inspection before migration. Field types (text, date, dropdown, number) are mapped to equivalent destination field types. Required-field constraints may cause import failures if the destination requires values that the source leaves blank.

Tags are flat label objects applied to Contacts and Deals. We preserve the tag taxonomy exactly and reapply all tags at import time. Tags that do not exist in the destination are created automatically.

User and Owner records map by email address. We match owners on email and assign records to the corresponding user in the destination. Users that do not exist in the destination are created as inactive placeholders with a note to activate.

Landing page forms and inline web forms are exported with field configurations and submission data. Form records are migrated as custom objects since form structures vary significantly across platforms and may not map 1:1 to a destination equivalent.