Migrate from GBuilder to HubSpot

GBuilder contact records map directly to HubSpot contacts. The primary company association resolves by matching GBuilder's primary_company_id to a HubSpot company by name. Contractor role information is preserved as a custom contact property (contractor_role) since HubSpot has no native role-on-project field.

GBuilder company records migrate to HubSpot companies with all standard fields (name, domain, industry, employee count). Companies without a name are flagged before migration so your team can assign a placeholder or merge them into an existing HubSpot company record.

GBuilder projects map to HubSpot deals. The project name becomes the deal name, budget becomes amount, project_status maps to a HubSpot deal stage via value mapping, and the primary contact on the project becomes the deal's associated contact. HubSpot deal stages are pre-defined per pipeline; we map GBuilder's status values to the nearest HubSpot stage name.

GBuilder stores project start and end dates as separate fields on the project record. HubSpot deals have only a single close_date property. During migration, we map the project end_date to the HubSpot close_date field and create two custom date properties: project_start_date__c to preserve the original start date and project_original_end_date__c to preserve the originally-scheduled end date if it differs from the current end date. These custom fields maintain full timeline visibility for reporting continuity within HubSpot's reporting tools.

GBuilder tasks migrate directly to HubSpot tasks with subject, description, due date, and status preserved. GBuilder task status values (pending, in_progress, completed) map to corresponding HubSpot task status values via a value-mapping transformation step. This ensures that completed tasks render correctly with the appropriate completed status in HubSpot's activity feed and task list views after migration completes.

GBuilder notes attached to contacts, companies, and projects migrate as HubSpot notes and attach to the corresponding contact, company, or deal record by ID. Rich-text formatting within GBuilder notes that contains HTML markup is preserved during migration where the HTML structure is compatible. Plain-text notes without formatting migrate without any transformation step required.

GBuilder file attachments are downloaded from the source system, re-uploaded to HubSpot's file manager, and associated to the corresponding contact, company, or deal record using the HubSpot record ID. File size limits apply per HubSpot's 25MB per-file constraint; any files exceeding this limit are flagged in the migration report for your team to split into smaller files or host externally with a link reference.

GBuilder user records are resolved by email address against HubSpot user accounts during migration. Any unmatched owners are flagged before the migration run commits; their records can either be assigned to a designated HubSpot fallback owner or the user can be provisioned in HubSpot's account management area before the migration run begins.

GBuilder custom properties unique to the construction domain such as trade_type, cost_code, change_order_number, change_order_amount, and project_location have no HubSpot native equivalent. Each becomes a HubSpot custom property that is created before the migration run begins. Type-aware mapping applies throughout: numeric fields map to HubSpot number properties, text fields map to single-line text properties, and currency fields map to number properties with currency formatting applied.

GBuilder project sub-items do not map to a single HubSpot object natively. Sub-items are aggregated into a custom text property on the deal (project_line_items__c) listing each sub-item as a formatted string, preserving the item name, quantity, and cost for reference. If sub-items require separate line-item tracking post-migration, your HubSpot admin can enable the Products object after migration completes.

HubSpot automatically sets the CreatedDate property at the time of import, which overwrites the original GBuilder create date. To preserve the original timestamps for historical reporting continuity and audit purposes, we capture both the original GBuilder createdate and updatedate as custom datetime properties on each HubSpot object. These custom fields are named original_created_date__c and original_updated_date__c respectively and are available for reporting in HubSpot's analytics tools.