Migrate from Real Estate 7 to Pipedrive

Real Estate 7 stores contacts as WordPress users or CRM contacts in its internal tables. Every contact maps to a Pipedrive Person record. Email, name, phone, job title, address, and owner assignment all migrate directly. Contacts without an associated company in Real Estate 7 land as standalone Persons in Pipedrive.

Agency and brokerage records from Real Estate 7 map to Pipedrive Organizations. Organization name, address, phone, website, and industry field carry over directly. Agents assigned to the agency in Real Estate 7 are linked via the Organization record in Pipedrive. Parent-child company hierarchies, if configured in Real Estate 7, translate to Pipedrive's smart links.

Each Real Estate 7 listing is a WordPress post with post_type='listing'. We convert each listing into a Pipedrive Deal: the listing title becomes the Deal name, the asking price maps to Deal value, and listing status (Active, Pending, Sold) maps to the corresponding Pipedrive stage. Property details (address, bedrooms, square footage) are stored as custom fields on the deal rather than as a separate object, since Pipedrive has no native property entity.

Real Estate 7 uses WordPress custom taxonomies (e.g., listing_category) to classify properties by type — Residential, Commercial, Land, Rental. Pipedrive has no native taxonomy equivalent. We create a custom picklist field (Listing_Category__c) on the Deal object and populate it with the source taxonomy term values. Your Pipedrive admin configures the picklist options before the migration runs.

Real Estate 7's property-type taxonomy (e.g., Single Family, Condo, Townhouse) migrates as a custom picklist field (Property_Type__c) on the Pipedrive Deal. Each taxonomy term becomes a picklist option in Pipedrive. If Real Estate 7 uses custom hierarchical taxonomies, we flatten the hierarchy into a dot-notation string stored in the custom field.

Real Estate 7 stores listing status as a WordPress taxonomy term or custom meta field. We map each status value to the corresponding stage name in your target Pipedrive pipeline: Active maps to your opening stage, Pending maps to your in-progress stage, and Sold or Closed maps to the winning stage. Stage mapping is defined per pipeline during the planning phase.

Unconverted leads in Real Estate 7 — contacts that expressed interest but did not yet become an active listing client — migrate as Pipedrive Leads. Pipedrive Leads inherit all custom fields defined on Deals (since Leads inherit dealFields), so any property interest captured in Real Estate 7 carries forward as a custom field on the Lead record for follow-up routing.

Phone call logs, meeting records, and notes from Real Estate 7's CRM section migrate as Pipedrive Activities. Call activities get Type='Call', meetings get Type='Meeting'. Notes with rich text content map to Pipedrive Notes. Original timestamps and assigned owner are preserved. Activities are linked to the parent Person or Organization record where the association exists in Real Estate 7.

Attachments stored against Real Estate 7 listings (photos, PDFs, contracts) or contact records are downloaded and re-uploaded to the corresponding Pipedrive record — Deal, Person, or Organization — as a Pipedrive File. File name and any available description are preserved. Pipedrive's 100MB per-file limit applies to uploaded attachments; files exceeding this threshold are noted for manual handling.

Real Estate 7 assigns contacts and listings to WordPress user accounts that function as CRM owners. We match each WordPress user to a Pipedrive user by email address. Unmatched WordPress users — those without a corresponding Pipedrive seat — are flagged before migration. Their records can be assigned to a fallback Pipedrive user or the WordPress user can be invited to Pipedrive before the migration runs.

Automations built inside Real Estate 7 — form-to-lead triggers, status-change notifications, email autoresponders, and CRM assignment rules — are tied to the WordPress plugin ecosystem and have no direct equivalent in Pipedrive. We export your automation definitions as a structured reference document your Pipedrive admin can use to rebuild equivalent rules in Pipedrive's native Automation builder.

Real Estate 7's visual presentation of listings on the WordPress website — featured image ordering, listing card layout, homepage featured listings — has no CRM-side equivalent in Pipedrive. We do not migrate website design configuration. Pipedrive's CRM configuration (pipeline stages, field labels, views, and dashboard cards) is set up based on your target-state requirements during the migration planning phase.

Pipedrive's native CreatedDate and UpdatedDate are set at the time of migration, not preserved from the source. For reporting continuity — particularly to show how long a listing has been on market — we store the original WordPress post date as a custom datetime field (Original_Listed_Date__c) on each Deal. This allows Pipedrive reports to reflect the full listing lifecycle regardless of when the migration ran.