Migrate from Agentbox to Pipedrive

Agentbox contact records (including names, phone numbers, email addresses, and postal addresses) map directly to Pipedrive People objects. The contact-agent links stored in Agentbox, which define which agent owns each contact, are resolved by matching the agent's email address against Pipedrive User accounts. The resolved Pipedrive User ID is written to the Person owner field. If an agent lacks a Pipedrive user account, the Person is flagged for fallback owner assignment, ensuring every migrated contact has a defined owner before migration completes.

Agentbox contact categories are tags applied to contacts (e.g., 'hot buyer', 'investor', 'vendor lead'). Pipedrive Labels are entity-scoped — we create Labels under the Person entity matching the category names, then apply them to each migrated Person record. Labels on other entity types (Deals, Organizations) are created separately if needed.

Agentbox stores buyer and tenant requirements (price range, property features, location preferences) against contact records. Pipedrive People do not have a native requirements field — we create custom text fields on the linked Organization record capturing the requirement data per contact, so the information is visible in the Organization context for agency-wide use.

Agentbox stores agency staff profiles containing names, phone numbers, and email addresses for internal personnel. These map to Pipedrive Organizations representing the agency's own team structure, preserving the contact details for internal staff records. When Agentbox maintains separate external company records, FlitStack maps those to Pipedrive Organizations linked to relevant Person records, ensuring both internal agency profiles and external company contacts are correctly represented in Pipedrive's organizational hierarchy.

Agentbox REA-sourced listing records (address, price, property type, status, listing date) have no direct Pipedrive equivalent. FlitStack maps listings to Pipedrive Deals with custom fields (Listing_Address__c, Listing_Type__c, Listing_Status__c, Listing_Price__c, REA_Listing_ID__c) preserving the property context alongside the deal. If a contact has multiple associated listings, multiple Deals are created with the Person linked.

Agentbox records the contact's role per listing (vendor, landlord, buyer, tenant). Pipedrive has no native role field on Person-Deal links. We store the role as a custom field on the Deal (Contact_Role__c) and link the Person to the Deal via the Deal's Person relationship — agencies can filter Deals by role using this custom field.

Agentbox enquiries recorded against listings (inquiry source, message content, enquiry date) map to Pipedrive Activities of type 'task' attached to the corresponding Deal. The activity subject captures the enquiry source and the body stores the message. Original enquiry timestamps are preserved on the Activity record.

Agentbox open home attendee records (attendee name, contact, attended listing, date) map to Pipedrive Activities of type 'meeting' linked to the Deal representing the listing, with a Note attached capturing the attendee details. If the attendee is not already a Person record in Pipedrive, a Person is created first, then linked.

Agentbox tasks and past appraisal records attached to contacts or listings map to Pipedrive Activities of type 'task'. Original due dates and task descriptions are preserved. The Activity is linked to the corresponding Deal (listing) and Person (contact) where associations exist.

Notes recorded against Agentbox contacts, listings, or appraisals transfer directly to Pipedrive Notes attached to the equivalent Person, Organization, or Deal record. The original creation timestamp and the agent who created the note are both preserved as metadata on the Pipedrive Note. Note body content is stored in the standard Note content field, maintaining the full text of the original entry. This direct mapping ensures all contextual information recorded in Agentbox remains accessible in the appropriate Pipedrive record context after migration.

Agentbox file attachments (documents, images linked to contacts or listings) are re-uploaded to Pipedrive's file storage and linked to the relevant Person, Organization, or Deal record. Pipedrive's file size limit (default 25MB per file) applies — large files are flagged before migration for manual handling if needed.

Agentbox contact-agent links define which agent owns each contact. FlitStack resolves the agent's email address against Pipedrive Users to set the Person's owner field. If an agent has no Pipedrive user account, the record is assigned to a fallback owner and flagged for review before the full migration runs.