Migrate from Camp Automation to Pipedrive

Camp Automation Contact records map directly to Pipedrive Person objects. We preserve name, email, phone, company association, and tag taxonomy. Email address serves as the dedupe key during import to prevent duplicate Person records. If the customer uses Camp's company association field, we resolve the linked Company to a Pipedrive Organization and attach it to the Person at import time.

Camp Automation Company records map to Pipedrive Organization. We preserve company name, domain, industry, and size fields. Organization is created before any Person import so that the Organization-Person link is satisfied at import time. Where Camp stores no separate Company record and Contacts are stored with inline company name, we create an Organization from the contact's company field and link it.

Camp Automation Deal records map to Pipedrive Deal. Pipeline stages in Camp (e.g., Lead, Qualified, Proposal, Negotiation, Won, Lost) map to named Pipedrive pipeline stages via a stage-to-stage mapping table defined during scoping. Deal value, close date, owner (by email), and any custom Deal fields migrate directly. We flag any Camp Deal without a linked Company as requiring an Organization to exist in Pipedrive before the Deal import begins.

Camp Automation's single deal pipeline maps to a single Pipedrive Pipeline with stages named to match the customer's Camp stage vocabulary. If Camp uses multiple pipelines (higher tiers), each maps to a separate Pipedrive Pipeline, which Pipedrive Starter and above support. Stage probability percentages transfer from Camp to Pipedrive stage probability fields.

Camp Automation Campaigns are multi-channel parent objects grouping email, SMS, social, and push notification assets. Pipedrive does not have a native multi-channel Campaign object. We decompose each Camp Campaign by channel, creating individual Activities in Pipedrive (email Activities, call Activities, meeting Activities) and tagging each with the original campaign name as an Activity label. The customer can filter Pipedrive Activities by campaign label to recreate the channel view.

Camp Automation email engagements (sent, received, logged) map to Pipedrive Activities of type email, linked to the corresponding Person or Deal. Email subject, body, timestamp, and direction (sent/received) migrate. Pipedrive's email sync feature can re-link email accounts post-migration for ongoing logging.

Camp Automation call engagements map to Pipedrive Activities of type call. Call duration, disposition, timestamp, and owner migrate to custom activity fields. ActivityDate is set to the original Camp engagement timestamp to preserve the activity timeline ordering.

Camp Automation meeting engagements map to Pipedrive Activities of type meeting. Meeting subject, date and time, duration, and attendees (Person links) transfer. Attendee emails are resolved to existing Pipedrive Person records or noted as unresolved for the customer admin to reconcile.

Camp Automation Notes (engagement type NOTE) migrate to Pipedrive Note records linked to the parent Person, Organization, or Deal. Note body and creation timestamp are preserved. Notes without a parent record are held in a reconciliation queue until the parent is resolved.

Camp Automation Task engagements map to Pipedrive Activities of type task with Status, Priority, and due date preserved. Task assignment migrates by resolving the Camp owner email to the Pipedrive User mapping established during scoping.

Custom fields on Camp Automation Contacts, Companies, and Deals require schema discovery before migration. Camp Automation does not expose field definitions via a public metadata API, so we request a full field list export from the Camp UI or a screen recording of the settings pages during discovery. Field types (text, date, dropdown, number, checkbox) are mapped to Pipedrive equivalent field types. Custom fields are pre-created in Pipedrive before record import begins to avoid type mismatches that corrupt reporting filters.

Camp Automation tags are flat label objects applied to Contacts and Deals. We preserve the tag taxonomy exactly and reapply all tags as Pipedrive Person labels and Organization labels at import time. Tags that do not exist in Pipedrive are created automatically during import. Tag strategy is confirmed with the customer during scoping.