Migrate from APTANIA CRM to Pipedrive

APTANIA Contact records map to Pipedrive Person. Standard fields (name, email, phone, address) migrate directly. The B2C/B2B flag stored in APTANIA is preserved as a custom field aptania_contact_type__c in Pipedrive. We set the Organization field during migration by resolving the APTANIA contact-to-company linkage against the imported Organization records.

APTANIA Company records map to Pipedrive Organization. Company name becomes the Organization name field and acts as the dedupe key. APTANIA's relational contact-company linkage is resolved before Person import so that each Person can be linked to its parent Organization at the time of insert. Any Company without a name is held for manual resolution.

APTANIA stores the contact-to-company association relationally. During migration we extract this linkage, build a name-based lookup table against the imported Organizations, and assign the resolved Organization ID to each Person's org_id field during import. Contacts without a matching Organization are imported as unlinked Persons and flagged for manual review post-migration.

APTANIA Deals map to Pipedrive Deals. Deal name, monetary value, expected close date, and stage name migrate directly. The APTANIA pipeline assignment is mapped to a pre-configured Pipedrive Pipeline before migration. Deal owner resolution happens by matching the APTANIA owner email to the imported Pipedrive User.

APTANIA stage names are extracted from the exported Deal records and mapped to Pipedrive Stage names within the target Pipeline. We configure the Pipeline and its stages in Pipedrive before migration so that stage values are valid at import time. Probability weights are approximated from the APTANIA stage sequence.

APTANIA pipeline structure is inferred from the exported Deal records. If multiple pipelines exist in APTANIA, we create corresponding Pipedrive Pipelines (one per deal pipeline) before migration. Single-pipeline APTANIA accounts use a single default Pipedrive Pipeline with configured stages.

APTANIA Activity logs map to Pipedrive Activity records with type matching. Call activities map to Pipedrive Call type, email activities to Email type, meeting activities to Meeting type, and notes to Note type. Activity timestamps migrate as the Activity date. The Who (Person) and What (Deal) references are resolved from the imported Person and Deal records using the email and deal ID as keys.

Pipedrive supports custom Activity Types beyond the standard call, email, meeting, and task. If APTANIA exports contain activity types outside this set, we create matching Activity Types in Pipedrive before the Activity import phase.

APTANIA custom field values migrate to Pipedrive custom fields. We create each custom field in Pipedrive during the pre-migration schema phase, matching the APTANIA field name as the Pipedrive field label and inferring the appropriate Pipedrive field type (text, number, date, varchar). Custom field metadata that is not exposed in the APTANIA export is documented in a separate field catalog for manual review.

APTANIA User records map to Pipedrive Users by email address. We resolve the owner reference on every Contact, Company, Deal, and Activity record before import. Users that do not yet exist in the destination Pipedrive account are held in a reconciliation queue and the customer's admin provisions them before record import resumes.

APTANIA's trigger-based email automation rules do not export. We do not migrate automation rules. We provide a pre-migration checklist that includes screenshot documentation of all active automation rules so the customer has a reference guide for manual rebuild in Pipedrive's Workflow feature (available on Advanced plan and above). This item is documented as a gap, not a mapping.

APTANIA's channel attribution data (referrer, UTM parameters, landing page history) is not exportable to standard file formats. Historical web engagement data is lost at migration. We recommend configuring fresh web tracking in Pipedrive via an integration with a third-party tool (such as Mailchimp, Zapier, or a marketing analytics platform) post-migration to preserve future attribution data.