Migrate from APRO CRM to Pipedrive

APRO's contact record maps directly to Pipedrive Person. Standard fields—first name, last name, email, phone, job title, primary address—transfer as-is. Any secondary phone numbers are stored in a custom phone‑2 field. Owner assignment is resolved by email match to a Pipedrive user; unresolved owners are queued for admin action. The contact’s primary property association is written to a custom property‑link field on the Person.

APRO's company entity maps to Pipedrive Organization. Core fields—company name, domain, website URL, industry pick-list, employee count, and annual revenue—migrate as Organization attributes. Parent‑company hierarchies in APRO translate to the Pipedrive parent_organization_id link. Any missing required fields are flagged before the migration run and can be supplied via supplemental CSV.

APRO deal records migrate to Pipedrive Deals. Each APRO deal pipeline is created as a separate Pipedrive pipeline, preserving stage order and probability settings. Stage names are matched one‑to‑one via a mapping table; any unmapped stages generate a warning for manual stage creation. APRO deal priority, custom deal values, and property references are stored in dedicated custom fields on the Deal.

APRO property records have no Pipedrive native equivalent. We map key property fields (address, type, listing status, asking price, automatch criteria) as custom fields on the related Person and Deal records. Full property-profile pages are exported as PDFs and attached to the corresponding Person record.

APRO listings are merged into Pipedrive Deals: the listing's asking price becomes the Deal amount, listing status maps to a Pipedrive stage, and property details migrate as deal custom fields. The original listing identifier is preserved as a reference field.

APRO's automatch settings (property criteria, client preference weights, matching algorithm parameters) have no Pipedrive equivalent. We export these as a JSON blob stored in a Pipedrive custom long-text field so the logic is preserved for manual reference and rebuild in Pipedrive Automations.

APRO IP-telephony call logs map to Pipedrive Activities with type=call. Call duration, disposition, recording URL (if external), and original timestamp are preserved. Call disposition values are mapped to Pipedrive's activity subject field since Pipedrive does not have a native disposition pick-list.

APRO email history migrates as Pipedrive Activities with type=email. The email subject, plain‑text body, and original timestamp transfer to the activity. Any HTML bodies are stripped to plain text to match Pipedrive’s note format. Owner assignment mirrors the Person’s owner. Email threading references (Message‑ID, In‑Reply‑To headers) are saved in a custom field to preserve conversation context within Pipedrive’s activity view.

APRO meeting records and notes migrate as Pipedrive Activities (type=meeting) or Notes respectively. Meeting start and end times, location, and attendee list are transferred to the activity; the attendee list is stored as a comma‑separated custom field. APRO’s note body maps to Pipedrive Note content, linked to the related Person or Deal record via the note’s linked_id and linked_type fields for full traceability.

APRO's autocreated document templates (contracts, property presentations) are binary files without a Pipedrive equivalent. We export them as attachments on the relevant Person or Deal record and flag them in a custom field so your team can manually reassociate them after migration.

APRO owner records are resolved to Pipedrive users by matching the email address field. If a Pipedrive user with the same email exists, the APRO owner’s user_id is written to the migrated record. Inactive or ghost owners without a match are assigned to a designated fallback Pipedrive user; all unmatched owners are logged in a separate CSV for admin review and invitation before finalization.

APRO's custom automation algorithms and business‑process workflows have no exportable format, so they cannot be transferred automatically. FlitStack AI extracts each workflow’s trigger, condition, and action definitions and writes them to a structured JSON file. Your Pipedrive admin can use this file as a reference to rebuild the logic in Pipedrive Automations, or recreate it in third‑party integration platforms such as Make (formerly Integromat) or Zapier.

APRO's built-in online messenger threads are stored in a proprietary format with no export endpoint. These conversations are not migratable to Pipedrive. We recommend archiving them in APRO before cutover and directing teams to use Pipedrive's email and activity logging for ongoing client communication.

APRO file attachments (property images, contracts, PDFs) are re-uploaded as Pipedrive Files linked to the corresponding Person, Organization, or Deal record. Files larger than Pipedrive's 100MB limit are split or hosted externally with a link stored in a custom field.