Migrate from Camp Automation to Twenty CRM

Camp Automation Contacts map to Twenty CRM's Person object. Standard fields (name, email, phone, company association) map directly. We resolve the company link by matching the Camp company_name to a Twenty Company record created earlier in the migration sequence. Any Camp custom properties on Contact require schema discovery before migration since Camp's custom field definitions are not exposed in a public metadata API.

Camp Automation Company records map to Twenty CRM's Company object. Company name, domain, industry, and size fields migrate directly. Twenty's Company object is created before Person import so that the company relationship is satisfied at Person insert time. If the destination Twenty workspace has no Company object created by default, we configure it via the API as a first step.

Camp Automation Deals map to Twenty CRM's Opportunity object. Deal pipeline, stage, value, and close date map to Opportunity stage, probability, amount, and close date. Stage naming conventions differ between platforms; we create a named stage-to-stage mapping during scoping. Custom properties on Deals require schema discovery and custom field pre-creation in Twenty before Deal import.

Camp Automation's multi-channel Campaign groups email, SMS, social post, and push notification assets under a single parent record. Twenty CRM has no native multi-channel Campaign object. We create a custom Campaign object in Twenty via the GraphQL API, import each Camp Campaign as a custom record, and tag channel-specific Person and Opportunity records with the campaign reference using Twenty's tag system. The unified multi-channel view does not survive the translation.

Camp Automation email templates include subject line, HTML body, and variable placeholders. We export templates as HTML with inline CSS preserved. Twenty CRM does not have a native email template object, so we create a custom Templates object via the API and store template content as TEXT fields. Template variable syntax is preserved as-is for the customer's admin to adapt to Twenty's placeholder format.

Camp Automation workflows define triggers (form submit, email open, deal stage change) and multi-branch action sequences. Twenty CRM's workflow builder is in active development and does not yet support the full trigger-action graph that Camp workflows use. We do not migrate automations as code. We document every Camp workflow with its trigger, conditions, and action sequence and deliver a written map for the customer's admin to rebuild in Twenty's workflow builder. Advanced Camp trigger types that have no Twenty equivalent are flagged explicitly.

Camp Automation's custom field definitions are not exposed in a public metadata API. Before migration, we prompt the customer to export the full field list from the Camp UI settings pages or provide a screen recording of Contact, Company, and Deal settings. We pre-create each custom field in Twenty via the GraphQL API with the correct field type (text, date, dropdown, number) before any data import. Field type mismatches can corrupt reporting filters in Twenty that depend on field type.

Same discovery process as Contact custom fields. Camp Company custom fields are exported via UI extraction, mapped to equivalent Twenty field types, and pre-created in the Twenty schema before Company import. If a Camp Company custom field references a picklist, we create a Twenty SELECT field with the same options preserved.

Same discovery process. Camp Deal custom fields are exported via UI extraction, mapped to equivalent Twenty field types, and pre-created as Opportunity custom fields in Twenty. We pay particular attention to currency fields (Deal value) and date fields (close date, expected close date) which require correct type mapping to avoid import rejection.

Tags are flat label objects applied to Contacts and Deals in Camp Automation. We preserve the tag taxonomy exactly and reapply all tags at import time. Tags that do not exist in Twenty are created automatically via the API at migration time. The tag taxonomy is preserved across both source and destination so that segmentation logic is not lost.

Camp Automation Owners map to Twenty CRM workspace users by email address match. We extract every distinct Owner referenced on Contact, Company, and Deal records. Owners without a matching Twenty User are held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive Camp owners migrate as inactive Twenty users.

Camp Automation engagements (calls, emails, meetings, tasks, notes) map to Twenty's activity tracking. We import engagement records with the original timestamp preserved as ActivityDate. The activity record is linked to the parent Person record via the Twenty relationship field. Call duration and disposition migrate to custom fields on the activity record.