Migrate from Bright to HubSpot

Bright contacts map directly to HubSpot contacts. Bright stores name, email, phone, job title, and address fields on the contact record — these map to HubSpot's equivalent contact properties. The Bright contact's associated company resolves to a HubSpot company via the contact-company association.

Bright companies map directly to HubSpot companies. HubSpot's company model includes name, domain, industry, employee count, annual revenue, and address fields. For multi-location Bright companies, each location can become a separate HubSpot company record, or a single company with multiple address entries, preserving city, state, country, and zip code so that geographic segmentation remains intact in HubSpot reporting.

Bright deals map to HubSpot deals, carrying deal name, amount, close date, and owner. The Bright deal stage maps to HubSpot's dealstage property. If Bright uses multiple pipelines, each maps to a separate HubSpot deal pipeline with its own stage configuration.

Bright's pipeline concept (if the account uses multiple deal pipelines) translates to HubSpot's native deal pipeline model. Each Bright pipeline becomes a separate HubSpot deal pipeline with its own set of stages, probability weights, and display order. The migration plan includes a pipeline-mapping matrix that links each Bright pipeline ID to its HubSpot counterpart, ensuring stage names, probabilities, and order are faithfully reproduced in the target account.

Bright deal stage names map to HubSpot deal stage names value-by-value. If Bright uses stage names like 'Proposal' or 'Negotiation', these map directly to HubSpot stages with the same names. Stage probability percentages are assigned from HubSpot's default stage configuration unless custom probabilities are specified.

Bright's activity records (calls, emails, meetings) map to HubSpot's engagement timeline. Each activity type appears as a distinct timeline entry on the associated contact or company record, preserving original timestamps, engagement direction (sent/received), and body content. Calls retain disposition outcomes, meetings retain start/end times, and email threads preserve subject and body, ensuring a complete historical record in HubSpot's activity feed.

Bright notes map to HubSpot notes on the associated contact or company record. The note body, created date, and owning user are preserved during import. Rich-text formatting present in Bright notes converts to plain text, and any embedded file links are reattached as HubSpot file associations. Timestamps retain the original date and time, allowing full chronological context in the HubSpot timeline.

Bright owner IDs resolve to HubSpot users by matching email addresses. Bright users without a corresponding HubSpot user are flagged before migration. Unmatched owners can be assigned to a fallback HubSpot user or the records can be imported without an owner for manual assignment post-migration.

Bright custom fields on contacts that have no direct HubSpot equivalent become HubSpot custom contact properties. Each custom property is created in HubSpot with a type matching the source field type (text, number, date, picklist). Custom property names in HubSpot follow a snake_case internal name convention.

Bright deal custom fields migrate as HubSpot deal custom properties. HubSpot deal custom properties are accessible from the deal record and can be included in deal views, workflows, and reports. The custom property must be created in HubSpot before the migration run.

Bright tasks map to HubSpot tasks on the associated contact, company, or deal record. All task fields—including subject, body, due date, priority, and owner—are preserved. HubSpot task statuses (not started, in progress, completed) correspond directly to Bright task completion flags, and any recurring task patterns are imported as individual task records with their original recurrence schedule intact.

Bright file attachments linked to contacts, companies, or deals are downloaded and re‑uploaded to HubSpot Files. Each file is attached to the matching HubSpot record, preserving the original filename, file type, and size. HubSpot's file storage limits per account tier apply, and large files are flagged for review if they exceed the tier's maximum upload size, ensuring compliance with HubSpot's storage policy.