Migrate your The Real Estate Platform (REP) data

The top-level organizational unit in REP. We map Region records and their associated child offices and metadata. Custom region-level fields require explicit field-level mapping.

Office records belong to a Region and contain team assignments, lead response time thresholds, and office-level branding. We preserve parent-region associations during migration.

Agent records are the core user accounts tied to offices. We migrate agent profiles including productivity dashboard settings, contact assignments, and agenda synchronizations.

Listings have complex lifecycle states and syndication targets. We map listing records with their status, associated agents, and property details, but syndication channel configurations may not export cleanly.

Lead records include source attribution, nurture campaign enrollment, and follow-up timestamps. We preserve lead status and assignment history but flag drip campaign state as requires re-enrollment.

Contact records can be associated with multiple agents and linked to listings or transactions. We deduplicate contacts and map contact-to-agent relationships explicitly in the destination system.

Transaction records track deals through stages. We migrate transaction metadata including status, associated contacts, listings, and agents, but note that REP may store transaction history differently than standard CRM deal objects.

On-demand and drip marketing campaigns are REP-stored objects. We export campaign definitions and enrollment lists but drip sequence state resets on import, requiring reactivation.

Every REP instance is uniquely configured with custom fields at the region, office, and agent levels. We extract the full custom field schema before export and map each field individually to destination equivalents.

Agent mobile app data including offline-created records and cached content is not accessible via the REP export interface. We document this gap and advise customers to sync before migration window.