Migrate from Camp Automation to Zoho CRM

Camp Automation stores all prospects as Contact records with a company link. Zoho separates unqualified prospects into Lead and qualified buyers into Contact. We apply a split rule during scoping using the customer's business logic (for example, Contacts with a status property below a defined threshold map to Zoho Lead; Contacts above that threshold map to Zoho Contact attached to an Account). We preserve the original Camp contact record identifier in a custom field camp_contact_id__c on both the Lead and Contact for audit. Accounts are created from Camp Company records before Contact migration to satisfy the Account lookup.

Camp Company records map directly to Zoho Account. Company name becomes Account Name, domain becomes Website, and industry and size fields map to standard Zoho Account fields. We use Account Name as the deduplication key during import. If the destination Zoho org uses Accounts in a B2B context, we create Account records before any Contact or Lead import so the lookup relationship is satisfied at insert time.

Camp Deals map to Zoho Deals with pipeline, stage, value, and expected close date preserved. We map Camp deal stages to Zoho Stages using a named stage mapping table since stage naming conventions differ. If Camp uses multiple deal pipelines and the destination Zoho edition supports multiple layouts, we configure a Zoho Stage for each unique pipeline-stage combination.

Camp Campaigns group email, SMS, social, and push notification assets under a single parent record. Zoho Campaigns module tracks campaign responses but does not natively hold the channel content assets. We import the Campaign as a Zoho Campaign record and migrate each channel's content as a separate Note attached to the Campaign, tagged by channel type. The Campaign name and target list (Contacts) migrate to Zoho Campaign for response tracking, but the visual multi-channel campaign view in the Camp UI does not replicate in Zoho.

Camp email templates include subject line, HTML body with inline CSS, and variable placeholders. We export templates as HTML and import them as Zoho Email Templates via the Templates API. Variable placeholder syntax is preserved; Zoho's {_field_name} syntax is applied where the customer's current template uses a different variable format. HTML rendering is validated during the sandbox migration pass.

Camp Automation custom field definitions require UI-based schema discovery since they are not exposed in a public metadata API. We prompt the customer to export the full field list from the Camp settings pages before migration begins. Each Camp custom field is mapped to a Zoho custom field of equivalent type (text, date, picklist, number, checkbox) during the Zoho module configuration phase. Zoho allows custom field creation during migration (up to 50 fields per module per edition). Field types are validated before import to prevent type-mismatch errors in Zoho reporting filters.

Tags from Camp Contacts and Deals migrate to Zoho Tags. Zoho imposes a limit of 10 tags per record and 25 characters per tag. We normalize tags that exceed 25 characters by truncating the label to 25 characters and flag the truncation in the reconciliation report. If a record in Camp has more than 10 tags, only the first 10 are migrated in Zoho's import order. Tags that do not exist in the destination are created automatically during import.

Camp Owners map to Zoho Users by email address match. We extract every distinct owner referenced on Contact, Company, Deal, and Engagement records and match against the destination Zoho org's User table. Owners without a matching Zoho User go to a reconciliation queue for the customer's admin to provision. Inactive Zoho Users can receive migrated records if the original Camp owner is no longer active.

Camp call logs migrate to Zoho Activities with Activity Type = Call. Call duration, disposition, and any notes attached to the call in Camp transfer to corresponding Zoho Activity fields. We resolve the parent Contact or Lead reference before inserting each Activity so the timeline links to the correct record in Zoho.

Camp email engagement records migrate to Zoho Activity records with type = Email. Email subject, body, and timestamp preserve. The parent Contact or Lead reference resolves at migration time using the email address as the linking key. If the email has attachments, we migrate them as Notes attached to the Activity record.

Camp meeting engagements map to Zoho Activities with Activity Type = Meeting. Start time, end time, location, and attendee list preserve. Attendee email addresses are linked to Zoho Contact or Lead records where matching users exist in the destination org.

Camp Notes attached to Contact, Company, or Deal records migrate as Zoho Notes linked to the corresponding Zoho record via the Notes API. Rich text formatting from Camp preserves as HTML in the Zoho Note body. Notes without a parent record are attached to the associated Account.