Migrate from Property Shell to HubSpot

Property Shell contract and interactive-map data has no native HubSpot home

Property Shell's contract management records — variation totals, upgrade flags, settlement dates — and its interactive map associations (stage, lot, release, sales status) are property-development constructs that do not exist in HubSpot's standard data model. FlitStack creates HubSpot custom objects (Contract, Property Unit) to preserve this data, but those objects require pre-creation in HubSpot before the migration loads. The migration plan includes the schema definition for these custom objects so your HubSpot admin can create them before data arrives. Without this step, contract and map data would land as unstructured notes or be omitted entirely.

HubSpot lifecycle stage is not a universal contact property in all tiers

HubSpot's lifecycle stage property is available on contacts by default but is a tiered feature — it functions fully in Marketing Hub Starter and above. When Property Shell contacts with lifecycle data land in HubSpot, the lifecycle stage values are preserved as a contact property, but any automated workflows that depend on lifecycle stage transitions need to be rebuilt in HubSpot Workflows. Property Shell's AI lead scoring similarly transfers as a static value at migration time; HubSpot Breeze AI provides ongoing scoring but must be configured post-migration rather than inherited from Property Shell.

Property Shell lead funnels and nurture journeys must be rebuilt in HubSpot Workflows

Property Shell's marketing automation features — lead nurture journeys, customised lead funnels, and automated follow-up sequences — are not part of the data migration. They have no export format that HubSpot's workflow engine can consume directly. FlitStack exports the Property Shell automation definitions as a structured document listing each workflow's trigger, conditions, and actions, giving your HubSpot admin or RevOps consultant a rebuild reference. The rebuild itself falls outside the data migration scope and is quoted separately as a HubSpot onboarding engagement.

Multi-project Property Shell portals require per-pipeline stage mapping in HubSpot

Property Shell portals managing multiple concurrent property development projects may use different stage labels across projects. Each Property Shell pipeline must be mapped to a corresponding HubSpot pipeline with stage names translated value-by-value. Stage probabilities in HubSpot are editable per pipeline and should be confirmed against your sales process before migration. If Property Shell stage labels are stored as free-text rather than pick-list values, FlitStack flags them for data cleansing before the value-mapping step to prevent orphan records in HubSpot.

Property Shell owner resolution to HubSpot users can leave records unassigned

Property Shell owner records are matched to HubSpot users by email address. If a Property Shell owner record uses an email domain that does not correspond to any existing HubSpot user — for example, a departed team member or an external consultant — the matched contact and deal records will not automatically assign to a HubSpot user. FlitStack generates an owner-resolution report before the migration runs, listing every unmatched owner and the count of records they own, so your team can decide whether to invite them to HubSpot, reassign their records, or use a fallback owner for the migration.