Migrate from The Real Estate Platform (REP) to HubSpot

REP Listing and Transaction objects require custom object schema design before migration

HubSpot has no native listing or transaction object — property listings from REP must be modeled as a HubSpot Custom Object with a schema your team defines (listing status, asking price, property type, bedrooms, square footage, and listing agent). Transaction financial fields (close amount, commission, payout status) append as custom properties on the HubSpot Deal. If your REP instance uses additional property subtypes (e.g., rental listings vs. sales listings), each subtype may require its own custom object definition or a property-type filter on a single custom object. We surface the full REP listing schema in the pre-migration audit so your HubSpot admin creates the custom object before data lands.

REP lead status values do not map directly to HubSpot lifecycle_stage without a value-mapping table

HubSpot's lifecycle_stage field uses a fixed set of values (Subscriber, Lead, MQL, SQL, Customer, Evangelist) and does not accept free-text values on import. REP lead status labels (New Lead, Contacted, Qualified, etc.) must be mapped to the closest HubSpot lifecycle stage value before any Contact record is written. If a REP label has no direct HubSpot equivalent, it must be stored in a custom Contact property instead — which means that dimension is invisible to HubSpot's native lead scoring and list segmentation until your admin rebuilds the logic in HubSpot workflows. We provide the mapping table in the pre-migration plan and your team approves the value assignments before the full run.

REP automated buyer follow-up sequences and drip campaigns do not export via the REP API

REP's automated buyer follow-up and drip marketing logic are stored as workflow definitions tied to REP's own automation engine. There is no documented API endpoint that returns sequence step order, delay rules, or trigger conditions. When migrating to HubSpot, this automation logic must be rebuilt manually using HubSpot workflow builder. FlitStack exports a structured JSON reference of your REP sequences (step order, delay between steps, content type per step, and associated deal-stage trigger) so your HubSpot admin has a rebuild guide. This is a manual configuration step, not a data migration operation, and must be scoped separately from the data migration timeline.

REP's Region and Office hierarchy does not map to any HubSpot native object

REP models organizational structure as Regions → Offices → Agents, with lead routing rules tied to this hierarchy. HubSpot has no native region or office object; the closest construct is HubSpot's owner model combined with HubSpot Teams (Enterprise tier). We map each REP region to a HubSpot Teams value and each REP office to a sub-team or custom property, but HubSpot's Teams feature requires a HubSpot Enterprise subscription. Teams on Starter or Professional tiers require a custom Teams property as a workaround, which does not support native team-based lead routing. Your team should confirm the HubSpot tier before migration so the organizational mapping strategy is set correctly.

REP's feature-based pricing model does not carry over — marketing contact billing is HubSpot-specific

REP charges on a per-feature basis across modules (CRM, marketing, transaction management, websites). HubSpot uses per-seat pricing for CRM seats plus optional add-on hubs (Marketing, Service, Operations). Teams migrating from REP's feature model to HubSpot's hub model often find that HubSpot's free CRM tier covers more REP-equivalent functionality than expected, but the HubSpot Marketing Hub carry-over from REP's automated marketing tools requires an additional paid subscription. We provide a feature-comparison worksheet during discovery so your team maps REP modules to HubSpot hubs and avoids duplicate purchases or coverage gaps.