Migrate from Camp Automation to Freshsales

Camp Automation Contacts map to Freshsales Contacts if the contact has an associated Company and the lifecycle stage indicates a qualified buyer (customer, evangelist, other). Camp Contacts with lifecycle stages of subscriber or lead without a company association map to Freshsales Lead. We compute the split using Camp's lifecyclestage property and the presence of a company association during scoping. The original Camp lifecycle stage is preserved in a custom field camp_original_lifecycle__c on both Lead and Contact for audit and reporting continuity.

Camp Automation Company records map directly to Freshsales Account. The company domain becomes the Account Website field and is used as the deduplication key during import. We create Accounts before Contact import so that the Account lookup is satisfied at Contact insert time. Industry, company size, and address fields map to Freshsales standard fields.

Camp Automation Deals map to Freshsales Deals with stage name translation. Camp dealstage values (e.g. Qualification, Proposal, Negotiation) are mapped to Freshsales stage values (e.g. New, Contacted, Proposal Sent, Closed Won, Closed Lost) using a named stage mapping defined during scoping. Deal value, close date, owner, and associated Contact and Company links migrate directly.

Camp Automation Campaigns are multi-channel objects that group email templates, SMS workflows, social posts, and push notification sequences under a single parent record. Freshsales does not have a native multi-channel Campaign object. We import the Camp Campaign as a Freshsales Campaign record and tag each channel-specific activity (email sends, SMS logs, social posts) with the campaign name as a tag, preserving the association for reporting even though the UI does not show a unified multi-channel view. The customer receives a written channel-to-campaign mapping document for manual reconstruction.

Camp Automation email templates with subject, HTML body, and variable placeholders are exported as HTML with inline CSS. We preserve the variable syntax as-is in the migration file. In Freshsales, templates use a different placeholder syntax (e.g., {{contact.first_name}} vs. Camp's native format), so we document the substitution mapping and the customer recreates templates in Freshsales with the translated syntax. Template content migrates as a reference document rather than a direct insert.

Tags are flat labels applied to Contacts, Companies, and Deals in Camp Automation. We preserve the tag taxonomy exactly and reapply all tags at import time using Freshsales Tags. Tags that do not exist in Freshsales are created automatically during migration. Tag-based segmentation is preserved for reporting continuity.

Camp Automation Users and Owners map to Freshsales Users by email address match. We resolve owners on email during import and assign records to the corresponding Freshsales User. Any Camp User without a matching Freshsales User is held in a reconciliation queue for the customer's admin to provision before record import resumes.

Camp Automation 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 or provide screen recordings of Contact, Company, and Deal settings. Without this, we risk creating Freshsales fields with incorrect types (text vs. date vs. dropdown), which corrupts reporting filters. We pre-create all custom fields in Freshsales with verified types before any data import begins. Custom field values migrate as CSV data against the pre-created schema.

Camp Automation automation workflows consist of trigger conditions (form submit, email open, deal stage change) and multi-branch action sequences. These do not migrate to Freshsales Workflows because the trigger-action models differ. We deliver a written inventory of every active Camp Automation workflow with its trigger type, conditions, action sequence, and recommended Freshsales Workflow equivalent, and the customer's admin rebuilds them post-migration.

Camp Automation landing page and inline web forms are exported with field configurations. Form structures vary significantly across platforms and Freshsales Webforms use a different builder model. We deliver a written inventory of form fields, conditional logic, and submission handling for the customer to rebuild in Freshsales Webforms. Form submission history migrates as Contact records if the submission included email address.