Migrate from Bloomr to Nutshell

Bloomr Contacts map directly to Nutshell Person records. We transfer name fields (first_name, last_name), email address, phone number, and any custom fields discovered during profiling. The Person record is created before any related Account to satisfy the lookup dependency. Bloomr's contact-level custom fields migrate to Nutshell custom fields created during schema design, with field types matched to Nutshell's supported types (text, number, date, picklist, checkbox). Email addresses serve as the dedupe key during import to prevent duplicate Person records.

Bloomr Company records map to Nutshell Account. We transfer company name, domain, industry, size, address, and any custom company properties. The Account record is created before Person records so that the Account lookup on Person is satisfied at insert time. Bloomr's domain field becomes the Account Website field if present. Custom company properties discovered during profiling migrate to typed Nutshell custom fields on Account.

Bloomr Deals map to Nutshell Deal records. We transfer deal name, value, stage, owner assignment, expected close date, and associated contacts. Bloomr stage values are mapped to Nutshell stage values during transformation, and if Bloomr uses a custom stage set, we create matching stages in Nutshell before migration. Deal owner resolves by matching the Bloomr owner email to a Nutshell user provisioned before the Deals phase begins.

Bloomr User records map to Nutshell User accounts. We resolve owners by email match across Contact, Account, and Deal records. Any Bloomr User without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Owner assignments on Deals and Contacts cannot proceed until this step is resolved because OwnerId is a required reference on most standard objects.

Bloomr call records map to Nutshell Activity entries with type preserved as Call. Call duration, disposition, and timestamp transfer to corresponding Activity fields. Activity ordering is preserved by setting the activity date to the original Bloomr timestamp. We load call records via Nutshell's Bulk API for volumes over 5,000 records to avoid REST timeout issues.

Bloomr email engagement records map to Nutshell Activity records with type Email. We transfer subject, body, timestamp, direction (sent/received), and the linked contact reference. If Bloomr exposes email thread threading data, we preserve it in a custom field for context. Email activity migrates via Bulk API when volume exceeds 5,000 records.

Bloomr meeting records map to Nutshell Activity entries with type Meeting. We transfer meeting title, scheduled date and time, duration, location, and attendee list (linked contacts). Meeting ordering and timestamps are preserved. If Bloomr provides attendee details per meeting, we link those contacts to the Activity record.

Bloomr task records map to Nutshell Activity entries with type Task. We transfer task subject, description, due date, status, and assigned owner (resolved via User mapping). Task completion status migrates directly. If Bloomr tasks are linked to specific Contacts or Deals, we resolve those Lookups and link accordingly.

Bloomr custom fields on any standard object (Contact, Account, Deal) are discovered during data profiling before migration begins. We create equivalent typed custom fields in Nutshell for each discovered field, matching the Bloomr field type to Nutshell's supported types. Multi-select or checkbox fields in Bloomr become Nutshell picklist or checkbox fields. The custom field mapping is validated in test migration before production begins. Custom field naming preserves the Bloomr label for admin recognition unless a naming conflict exists in the destination.