Migrate from Atendare to Pipedrive

Atendare Contact records map to Pipedrive Person. Email, phone, name, and owner assignment migrate directly. Atendare's segmentation tags transfer to Pipedrive custom fields (multi-select or varchar depending on tag volume). Lifecycle stage or contact status from Atendare maps to a custom varchar field rather than a native Pipedrive field since Pipedrive does not have a built-in lifecycle stage property.

Atendare Company records map to Pipedrive Organization. Company name, domain, industry, and address fields migrate directly. Custom fields on Atendare Company records map to Pipedrive Organization custom fields created before import. The Organization record is created before the Person import so that the org_id reference is available during Person insert.

Atendare Deals map directly to Pipedrive Deals. Deal name, value, stage, expected close date, and owner migrate. Stage names from Atendare are mapped to Pipedrive stage IDs during configuration, and the mapping is applied as a transform before import. Atendare deal custom properties map to Pipedrive Deal custom fields.

Atendare's pipeline stages (configurable per account) map to Pipedrive Pipeline stages. We create the Pipedrive Pipeline structure before migration, matching Atendare stage names to Pipedrive stage labels and probabilities. If the customer has multiple Atendare pipelines, we create corresponding Pipedrive Pipelines on the Advanced plan or higher; Lite plan migrations consolidate to a single pipeline.

Atendare activities (calls, meetings, tasks) map to Pipedrive Activity with the type field set to call, meeting, or task respectively. Timestamp, duration, description, and owner assignment preserve. Pipedrive Activity uses a single Activity object with a type discriminator, whereas Atendare uses separate activity records per type. This is a structural difference we resolve during the transform step. Note: if Atendare API access is unavailable and only CSV exports are possible, Activities typically do not export in row-based format and are flagged as a limitation.

Atendare Team Members mapped as Deal owners and Activity owners resolve by email match against Pipedrive Users. The customer provisions Pipedrive user accounts before migration begins. Any Atendare owner without a matching Pipedrive User goes to a reconciliation queue; migration cannot proceed on records with unresolved OwnerId references.

Atendare custom fields on Contacts, Companies, and Deals vary by account configuration. We detect all custom property definitions during discovery, infer field types (varchar, int, date, email, phone) from sample values, create equivalent Pipedrive custom fields before migration, and map source values to the typed destination field. Custom field mapping is validated during the test migration before production import.

Atendare email campaign metadata (name, target segment, send date) can be recorded as a Pipedrive Activity of type email_note if the API exposes it. Actual email body HTML and template content do not have a direct Pipedrive equivalent. We flag email campaign content for manual export or recommend a dedicated email marketing tool (Mailchimp, ActiveCampaign) post-migration. Campaign tracking metrics (open rate, click rate) do not migrate as records.

Atendare Landing Pages (Pro and Enterprise tiers) are platform-hosted assets with no standalone data model exposed via documented API. We do not migrate landing page content. We flag the existence of any landing pages during discovery and recommend the customer export HTML manually or plan to rebuild in a dedicated landing page tool. The written inventory we deliver includes landing page URL, form fields, and traffic source for the customer's admin to reference during rebuild.

Atendare Proposals (Enterprise-tier feature) include line items, totals, and status. Pipedrive does not have a native Proposal or Quote object in the Lite or Advanced plans. We extract proposal data where accessible and store it as a Pipedrive Product record linked to the Deal, or as a custom field on the Deal capturing proposal total and status. The customer evaluates whether a third-party quoting tool (PandaDoc, Qwilr, or similar) is needed for ongoing proposal generation.