Migrate from Camp Automation to HubSpot

Camp contacts map 1:1 to HubSpot contacts. Email is the primary deduplication key. Unsubscribed status from Camp maps to HubSpot's email opt-out property (hs_email_optout). Camp contact IDs are stored as a custom HubSpot property (camp_contact_id) for traceability. All standard HubSpot contact properties (firstname, lastname, phone, jobtitle, address) are created automatically during the import process.

Camp companies map to HubSpot companies. Camp stores address fields individually (address, city, state, country, zip); these collapse into HubSpot's structured address property. HubSpot's domain-based company creation is disabled during migration to prevent duplicate companies for the same domain. If multiple Camp companies share the same domain, they are consolidated into a single HubSpot company with all relevant contact associations preserved.

Camp deals map to HubSpot deals. Each Camp deal carries a pipeline name and stage name that must be mapped to a HubSpot deal pipeline and stage pick-list. If no matching HubSpot pipeline exists, FlitStack creates one using Camp's pipeline name before the deal import runs.

Camp stores pipeline names as a deal field. HubSpot requires a named pipeline object with its own stage pick-list. FlitStack reads all unique pipeline names from Camp deals, creates corresponding HubSpot pipelines, and maps each Camp stage value to a HubSpot stage with the same display name.

Stage names from Camp are mapped one-by-one to HubSpot stage values within the corresponding pipeline. Closed-won and closed-lost status resolves to HubSpot's dealstage closedwon and closedlost values. Stage probability values from Camp are stored as a HubSpot custom property for reporting continuity.

Camp stores owner ID on contacts and deals. FlitStack resolves Camp owner IDs by email lookup against HubSpot users. Any Camp owner whose email does not match a HubSpot user is flagged before migration and can be reassigned to a fallback HubSpot owner or invited to HubSpot first.

Camp call and email activity records map to HubSpot Tasks with Subject, body, and completion timestamp preserved. HubSpot's Task Type field is set to Call for phone records and Email for email records. Original Camp owner is preserved as the HubSpot task owner via email resolution.

Camp meeting records with start time, end time, and attendees map to HubSpot Events. HubSpot's event owner is resolved by email. Attendee contact associations from Camp are stored in the HubSpot Event's body text for manual review and re-creation in HubSpot's meeting link feature.

Every Camp custom field on Contact, Company, or Deal becomes a HubSpot custom property. FlitStack reads the Camp field type (text, number, date, picklist, checkbox) and creates the corresponding HubSpot property with the same field type. Required flag and default value are preserved where supported.

Camp tags on contacts migrate to HubSpot's built-in tags property (contacts are tagged with a comma-separated list). Tags appear in HubSpot contact records and can be used in HubSpot lists and workflows after migration. After the migration completes, your HubSpot admin can create dynamic lists based on tag membership or use tags as filter criteria in HubSpot workflows to trigger automated actions.

Camp's contact scoring values migrate to a HubSpot custom number property (camp_contact_score) on the contact. HubSpot's native contact scoring (if enabled on the Sales Hub plan) can take over after migration; the Camp score is preserved as a reference field during the transition period.

Camp's contact-to-company or contact-to-deal role labels have no native HubSpot equivalent. FlitStack stores label names as a custom text property on the association for reference. Teams must manually rebuild role labeling in HubSpot using custom properties or the built-in association labels feature if available in their HubSpot edition.

Camp workflows, automation rules, and enrollment triggers do not migrate. FlitStack exports Camp workflow definitions in a structured JSON format that HubSpot admins can use as a reference when rebuilding automations in HubSpot's workflow builder. This export is delivered before the data migration runs.