Migrate from Agentbox to HubSpot

Agentbox contacts map directly to HubSpot contacts. Standard fields (first name, last name, email, phone) use HubSpot's native properties. Agentbox contact categories (tags applied in the source CRM) are migrated as HubSpot contact properties or contact labels depending on your HubSpot plan.

Agentbox company records map to HubSpot companies. HubSpot company records support a parent-company hierarchy — if Agentbox uses multi-office agency structures, we map the agency as the parent Company and each office as a child Company linked via Parent Company ID.

Agentbox deal records map to HubSpot deals. Each deal maps to the associated HubSpot contact and company via standard association fields. Deal stage names in Agentbox are mapped value-by-value to HubSpot deal stages; we preserve the original close date and deal owner from Agentbox.

Agentbox buyer requirements (price range, bedroom count, property type, preferred suburbs, timeline) are a child record linked to a contact. Since HubSpot has no native buyer-requirement object, we decompose each requirement field into a named custom property on the HubSpot contact record (e.g. Buyer_Price_Min_c, Buyer_Bedrooms_c, Buyer_Property_Type_c).

Agentbox listing records have no native HubSpot equivalent. We create a Listing__c custom object in HubSpot with properties for address, suburb, state, postcode, listing status, asking price, and listing agent. Contacts linked to listings in Agentbox are associated via a custom junction object or HubSpot's associations API.

Agentbox appraisal records store estimated property value, appraisal date, and the conducting agent. HubSpot has no native appraisal object, so we create an Appraisal__c custom object with properties for estimated value, appraisal date, and a lookup to the Property custom object and the conducting agent (HubSpot user).

Agentbox agent profiles (name, role, phone, email, assigned office) map to HubSpot users. Email-matched agents resolve directly to HubSpot user accounts. Agents without a HubSpot user account are flagged for your team to create accounts before migration or assigned to a placeholder owner.

Agentbox office records map to HubSpot company records as child entries under a parent agency Company. Office-level properties such as office name, office code, and office address are migrated as custom properties on the child Company record. This translation preserves the multi-office hierarchy that Agentbox manages natively, ensuring each branch retains its distinguishing attributes within HubSpot's parent-child company structure for accurate office-level reporting and branch identification.

Notes attached to contacts or companies in Agentbox migrate as HubSpot engagement notes. The note body, author (owner), and original create date are preserved. Call and meeting records from Agentbox migrate as HubSpot calls and meetings with original timestamps and owners.

Agentbox contact categories are flat string tags (e.g. 'Hot Buyer', 'Vendor', 'Tenant'). These map to HubSpot contact properties if the tag represents a classification, or to HubSpot contact labels if your plan supports them. Custom categories are created as HubSpot contact properties with the same option values.

Agentbox links contacts to listings in a many-to-many relationship (e.g. a buyer linked to multiple properties, or a vendor's property linked to their contact record). Since HubSpot lacks a native listing object, we either link the contact to the Listing__c custom object via a junction, or create a HubSpot deal associated with the contact and the Listing__c record to represent the active engagement.

Agentbox pulls live CoreLogic data (on-market signals, automated valuations, suburb analytics) through a native integration. This data is sourced by Agentbox at query time and is not stored as a persistent record in the Agentbox database available for export. Market data must be re-established in HubSpot through a separate CoreLogic integration or manual enrichment.