Migrate from Bright to Pipedrive

Bright contacts map directly to Pipedrive People, using the email address as a unique identifier. Each contact's primary company resolves to an Organization record that must exist first in Pipedrive; unassigned contacts create as People without an organization link. Original create dates and owner assignments are preserved, and the Bright contact ID is stored in a custom field for traceability.

Bright companies map to Pipedrive Organizations, preserving company name, domain, industry, and address details. Parent-child hierarchies in Bright translate to Pipedrive's parent organization field on the child record, with circular references detected and flagged before migration. Organization IDs are stored in a custom field for later reconciliation.

Bright deals migrate to Pipedrive Deals, preserving deal title, value, currency, and close date. Each deal must link to an existing Organization and optionally to one or more People; the link is created after Organizations and People are loaded. Deal status maps to a Pipedrive Pipeline stage using the stage name mapping defined per pipeline, while probability percentages are noted for manual entry in Pipedrive's stage settings.

Each Bright pipeline creates as a Pipedrive Pipeline with its own set of stages, preserving stage order and names. Pipedrive Pipelines are account-level containers for deal progression, and stage names map value-by-value from Bright using the migration plan. Pipelines must be created before deals load, and visibility groups can be set per pipeline during setup.

Bright pipeline stage names map to Pipedrive stage names per pipeline, preserving stage order and any win/loss flags. Probability percentages associated with each stage in Bright do not transfer natively; they are documented for manual re-entry in Pipedrive's stage settings. Any stage-specific email templates or automation triggers are noted in the migration plan for later recreation.

Bright leads that have not yet converted to contacts map directly to Pipedrive Leads, preserving lead status, source, and any conversion date if applicable. Pipedrive Leads share the same custom fields as Deals on the same account, simplifying mapping for accounts that use both objects. The migration plan includes a mapping table for lead-specific fields such as rating, source, and lifecycle stage to ensure continuity after cutover.

Bright call logs migrate as Pipedrive Activities with type=Call, preserving subject, duration, outcome, owner, and original timestamp. Call notes are stored in the activity's description field, and the Bright activity ID is recorded in a custom field for traceability. Activities are linked to the relevant Person, Organization, or Deal after those records have been loaded into Pipedrive.

Bright email engagement records migrate as Pipedrive Activities with type=Email, preserving subject, timestamp, and thread ID. Full email body text is stored in the activity's description field, as Pipedrive does not retain the full body by default. Attachments are downloaded from Bright and re‑uploaded to the activity's file section, with a reference to the original Bright attachment ID for audit trail.

Bright meetings migrate as Pipedrive Events, preserving start time, end time, subject, location, and any meeting notes or recurrence patterns. Participants are matched to Pipedrive People by email address; unresolved participants are added as guests with their email recorded. Custom fields attached to the Bright meeting are transferred to the Pipedrive Event custom fields after the target fields are created.

Bright notes migrate as Pipedrive Notes attached to the relevant Person, Organization, or Deal record, preserving the original author, created timestamp, and any tags or categories. Rich-text formatting is converted to plain text to ensure Pipedrive compatibility, and any embedded file attachments are downloaded and re‑uploaded to the note's file section, with a reference to the original Bright file ID for audit purposes.

Bright products or line items map to Pipedrive Products, preserving product name, description, pricing, currency, and unit of measure. Custom fields on Bright products transfer to Pipedrive Product custom fields after those fields are created in the target account. Products are loaded before Deals so that deal‑product links can be established using Pipedrive's deal‑product association, and any inactive products are flagged for review.

Bright file attachments are downloaded from Bright's storage and re‑uploaded to Pipedrive Files, preserving the original file name, size, and upload timestamp. Large files are uploaded in chunks to respect Pipedrive's file size limits, and inline images embedded in notes are extracted, re‑uploaded, and referenced in the note. The migration audit log records each file transfer with its source Bright ID for traceability.

Bright custom fields create as Pipedrive custom fields on the target account before migration runs. Pipedrive field keys are account-specific hashes — the migration plan lists each Bright field with its target field key and field type for accurate mapping.

Bright users resolve to Pipedrive users by matching email addresses, preserving active/inactive status and role information. Unmatched owners are created as Pipedrive users and flagged with the original Bright owner ID in a custom field for reference. This user mapping step is a prerequisite for all record migrations, ensuring that owner links are valid from the first load. A user mapping table is delivered with the migration plan.