Migrate from Zavvie Power Buyer to Pipedrive

Property records have no Pipedrive native equivalent — custom fields on Deals are the only option

Zavvie's Property object stores listing address, MLS number, and property type. Pipedrive has no property or listing object — every property detail becomes a custom field on the Deal or Person record. If your brokerage tracks multiple properties per transaction (rare but possible in buy-before-you-sell scenarios), you cannot represent that as a sub-object in Pipedrive; you either create multiple linked Deals or collapse into one Deal with a multi-value custom field. We flag multi-property deals during discovery and surface the mapping decision before migration so you choose the representation that matches your reporting needs.

Pipedrive's API v2 rate limits require batch sizing and retry logic — large migrations need throttle management

Pipedrive introduced token-based rate limits in December 2024 for API requests. New customers are immediately affected; existing accounts have a phased rollout through 2025. The rate limit caps requests per minute per API token, which means bulk imports of 50,000+ offers and 20,000+ contacts need chunking with exponential backoff on 429 responses. FlitStack's migration engine implements token-level rate limit tracking and pauses between batch submissions to avoid throttling. If your brokerage has an existing Pipedrive account with a mature API token, we measure the actual throughput during the sample migration and calibrate batch sizes accordingly.

Power Buyer program type is a billing-adjacent field with no direct Pipedrive equivalent

Zavvie's program type (Cash Offer vs Buy Before You Sell) determines how your brokerage's mortgage capture revenue is attributed — Cash Offer connects buyers to the preferred lender directly, while Buy Before You Sell involves a bridge-financing component. Pipedrive has no built-in field for program attribution; we create Program_Type__c as a custom pick-list on Deal. This works for filtering and reporting, but Pipedrive's native revenue attribution model (Revenueplit__c, Weighted_Amount__c) does not natively segment by program type — you need a custom report or a BI tool to slice revenue by program in Pipedrive.

Zavvie agent-to-brokerage assignments require manual reconstruction in Pipedrive Organization hierarchy

Zavvie stores agent assignments at the offer level (which agent owns the offer) and at the brokerage level (which agents belong to which brokerage). Pipedrive's Organization hierarchy represents the brokerage tree but does not have a native 'agent within brokerage' relationship object — agents are Pipedrive Users attached to the Organization as the owner of their deals, but there is no 'member of Organization' record type. We map agent assignments to Pipedrive Users and link their deals to the Organization, but team-based visibility and sharing rules that depend on brokerage hierarchy need Pipedrive's visibility group configuration after migration.

Offer document attachments must be re-uploaded to Pipedrive Files — no direct file URL migration

Zavvie stores attachments (purchase agreements, lender letters, inspection reports) as hosted files. Pipedrive's Files feature requires re-uploading binary data — there is no URL-import option for external file hosting. We download Zavvie attachments and upload them to Pipedrive via the Files API, associating each file with the matching Deal or Person record. Files exceeding Pipedrive's 25MB per-file limit are flagged before migration for pre-upload compression. If you use a document management system (Box, Dropbox) linked to Zavvie, those integrations must be rebuilt in Pipedrive.