Migrate from Apptivo to Pipedrive

Apptivo Contacts map directly to Pipedrive Person records. Standard fields (name, email, phone, address) map 1:1. Per-app custom attributes from the Apptivo CRM Contacts Master Layout migrate to Pipedrive custom fields scoped to the Person object. We enumerate every custom attribute in the Contacts app during discovery to prevent silent field collision with identically named attributes in other Apptivo apps.

Apptivo Leads with lead score, source tracking, and lifecycle stage map to Pipedrive Lead. The leadscore property migrates to a numeric custom field. Lead status (New, Contacted, Qualified, Lost) maps to Pipedrive's Lead Status picklist, with custom values created in the destination if the source statuses do not match Pipedrive defaults.

Apptivo Customers (B2B account records with associated contacts and addresses) map to Pipedrive Organization. Company name, website, industry, and billing address migrate to the corresponding Organization fields. We link any associated Apptivo Contacts to the Organization after the Organization is created, satisfying Pipedrive's Person-Organization relationship requirement.

Apptivo Opportunities (deals tracked through pipeline stages with revenue and expected close date) map to Pipedrive Deal. Deal stage names migrate to Pipedrive stage values within the configured pipeline. Deal amount, expected close date, and owner assignment transfer directly. Stage probability percentages from Apptivo migrate to the corresponding Pipedrive stage probability if the destination pipeline is configured to use custom probabilities.

Apptivo Cases with priority, status, owner, and conversation threads require a destination decision. Pipedrive Professional and above include a native Cases add-on. If the customer licenses Cases, we map ticket data directly to Pipedrive Case records with status mapped to Case Status and conversation threads preserved as linked Activity records. If Cases is not licensed, we map Case data to custom Deal fields or a custom Activity type as a fallback.

Apptivo Items (product and service catalog items with pricing and custom attributes) map to Pipedrive Products. Item name, code, description, and pricing migrate to the corresponding Product fields. Custom attributes on Items map to Pipedrive Product custom fields.

File attachments on Apptivo records are stored in Apptivo's file system and may hit export size limits for large files. We extract file blobs via the Apptivo API, upload them to Pipedrive's document attachment endpoint, and link them to the parent record (Person, Organization, or Deal) using the file URL reference. Files exceeding Pipedrive's attachment size limits are flagged for manual review.

Apptivo Employee records map to Pipedrive Users for owner assignment. We match Apptivo employee email to Pipedrive User email as the reconciliation key. Any Apptivo Owner without a matching Pipedrive User is held in a reconciliation queue for the customer's admin to provision before record import resumes. Inactive employees map to inactive Pipedrive Users to preserve historical assignment.

Apptivo Project records with tasks, milestones, and assignees map to Pipedrive Projects (a paid add-on available from Growth plan onward). Task hierarchies and milestone dates migrate to Pipedrive Project task structures. Projects on Lite or Essential plans require either upgrading to Growth or using a project management integration (Asana, Trello, or similar) as a workaround.

Every Apptivo custom attribute across all active apps is enumerated during discovery. Each attribute maps to a Pipedrive custom field scoped to the corresponding object (Person, Organization, Deal, Lead). We preserve the original Apptivo attribute type (text, number, date, dropdown, radio) and map to the nearest Pipedrive field type. Dropdown and radio attributes from Apptivo migrate as Pipedrive picklist values. This per-app enumeration is the most time-intensive part of the scoping phase for multi-app Apptivo customers.