Migrate from Rechat to HubSpot

Rechat contacts migrate as HubSpot contacts. The primary company association maps to HubSpot's company association via the company name or domain match. Rechat contact properties become HubSpot contact properties — standard ones map directly, custom ones require HubSpot custom property creation.

Rechat companies migrate as HubSpot companies. The company name maps directly to the HubSpot company name property. Address components (street, city, state, zip, country) map individually to HubSpot's address property fields. Phone and domain map to company phone and website respectively.

Rechat deals migrate as HubSpot deals. The deal name, transaction amount, close date, and owner map directly to HubSpot deal properties. The Rechat deal status value (Active, Under Contract, Closed) maps to HubSpot deal stage via value-by-value mapping, and the mapping plan is surfaced before migration runs so you can adjust stage assignments.

Rechat users and owners resolve to HubSpot owners by matching email addresses. Unmatched Rechat users are flagged before migration so your HubSpot admin can either invite them or assign their records to a fallback owner. This owner resolution step is required before deals can be assigned in HubSpot.

Rechat notes migrate as HubSpot notes on the associated contact, company, or deal record. Note body text maps directly. Rich-text formatting in Rechat notes is preserved where possible, and inline images are downloaded and re-uploaded to HubSpot Files with the note reference updated.

Rechat file attachments associated with contacts, companies, or deals re-upload to HubSpot Files. Each file is attached to the correct HubSpot record by ID. Files exceeding HubSpot's 25 MB per-file limit are flagged so your team can store them externally and preserve a link in a custom property.

Rechat's deal pipeline stages map to HubSpot deal stage values via a value-by-value table. Rechat's standard stages (Active, Under Contract, Closed Won, Closed Lost) map to the closest HubSpot deal stage names, with the mapping documented in the pre-migration plan so your team can adjust stage names before the migration runs.

Rechat's Lucy AI assistant generates notes and property insights that are stored as structured fields on the contact or deal. These do not map to a native HubSpot object — they become a custom multi-line text property (Lucy_Notes__c) on the relevant HubSpot record for reference and audit continuity.

Rechat tags applied to contacts or deals do not have a native HubSpot equivalent. Tags migrate as a custom property (Rechat_Tags__c) — a multi-select pick-list or text field depending on the volume of unique tags. High-cardinality tag sets may be collapsed to a text field to avoid HubSpot pick-list value limits.

Rechat custom objects (if your plan includes them) migrate as HubSpot custom objects. This is only available on HubSpot Enterprise tiers. The migration plan documents the association model between Rechat custom objects and standard objects so HubSpot's relationship structure can be replicated correctly.

The original listing source in Rechat (which MLS or portal the listing came from) migrates as a custom pick-list property (Listing_Source__c) on the deal record. Since HubSpot has no native listing source field, this custom property preserves the attribution data for reporting continuity.

The Rechat internal record ID is stored as a custom property (Rechat_ID__c) on every migrated record. This serves two purposes: it enables delta-run de-duplication on subsequent migrations and provides a traceable reference back to the source Rechat record for audit and reconciliation.