Migrate from Bright to Nutshell

Bright's Person (contact) records map directly to Nutshell People. All standard fields — name, email, phone, address, title — transfer as-is. A Bright Person without a company link becomes a standalone Nutshell Person. Original create and update timestamps are preserved as metadata fields for reporting continuity.

Bright records flagged as leads (status = 'lead' or equivalent) map to Nutshell Leads. Nutshell Leads have a different field set than People — they include lead source, status, and rating fields that do not exist on People. FlitStack maps the relevant Bright lead-status and source fields to Nutshell's Lead object fields and sets the Lead status to 'New' by default for migrated records.

Bright Company records map 1:1 to Nutshell Companies. Standard fields — name, website, industry, phone, address — transfer directly. Nutshell's Company object does not use a parent-child hierarchy like some CRMs; multi-level company structures in Bright flatten to individual Nutshell Company records linked to People via the People record.

Bright Deals map to Nutshell Deals with deal name, value (amount), stage, and expected close date preserved. Nutshell Deals are tied to a Pipeline — FlitStack maps Bright's pipeline name to a Nutshell Pipeline object, creating it if it does not exist, and then associates all Deals to that Pipeline. Stage-by-stage probability values are reapplied based on Nutshell's stage configuration.

Each Bright pipeline becomes a Nutshell Pipeline object. Bright's stage names, probabilities, and stage order transfer to Nutshell stage definitions. If Bright uses a single pipeline, a single Nutshell Pipeline is created. Multiple Bright pipelines create multiple Nutshell Pipelines — teams configure which pipeline view appears by default in Nutshell settings after migration.

Bright tasks map to Nutshell Tasks. Task subject, description, due date, completion status, and owner transfer. Tasks are linked to the parent Nutshell record (Person, Company, or Deal) by matching the Bright record ID preserved in Nutshell's integration reference field. Incomplete tasks retain their due date; completed tasks preserve completion date.

Bright logged calls map to Nutshell Calls with subject, duration, direction (inbound/outbound), and outcome notes preserved. Bright meetings map to Nutshell Meetings with start/end times, location, and invitee list. Both are linked to the parent Person or Deal in Nutshell using the preserved Bright record ID.

Bright email logs (sent/received records) migrate as Nutshell Activities attached to the Person record. The email subject becomes the activity subject; the email body becomes the description. If Bright stores threaded email history, each message becomes a separate activity entry in chronological order. Bounce or delivery status flags are not transferred as Nutshell does not track email delivery status natively.

Bright notes map to Nutshell Notes attached to the parent record. Note title and body text transfer. If notes contain HTML formatting, the text is preserved and HTML stripped — plain-text note content is what Nutshell renders in its UI. Timestamps and owner attribution are preserved.

Bright custom fields on Person records create corresponding Nutshell custom fields on the Person object. Field type mapping: text → text, number → number, date → date, picklist → choice (with values mapped one-by-one), checkbox → boolean. FlitStack creates the Nutshell custom fields before the migration run and maps values during data transfer.

Bright custom fields on Company records create Nutshell custom fields on the Company object. Same type-mapping rules apply as for Person custom fields. If Bright stores multi-select picklist values in a custom field, Nutshell's choice field stores the comma-separated values as a single string — your team decides whether to split this into separate choice values post-migration.

Bright custom fields on Deal records create Nutshell custom fields on the Deal object. These appear on the Deal detail page in Nutshell. If Bright stores deal-specific metrics (e.g., win probability override, competitor tracked, decision-maker name) these appear as custom fields on the Nutshell Deal.

Bright user records are resolved against Nutshell users by email address match. A Bright owner assigned to a record migrates to the Nutshell user with the matching email. If no match exists, the record is assigned to the migration fallback owner you designate before the run. FlitStack generates an unmatched-owner report so you can invite missing users before or immediately after migration.

Bright file attachments on People, Companies, or Deals are downloaded and re-uploaded as Nutshell file attachments. Files are associated with the correct Nutshell record based on the Bright record ID mapping. Nutshell stores files linked to the parent record; inline images in notes are extracted and reattached as separate files.

Bright tags on any record type map to Nutshell Tags. Tags are stored as a tag array on the Nutshell record — there is no separate tag object. If Bright uses a hierarchical tag taxonomy, only the leaf-level tags transfer, as Nutshell does not support nested tag hierarchies.