Migrate from Makesbridge to Nutshell

Makesbridge Subscribers map to Nutshell People if they have an associated company and account relationship, or to Nutshell Leads if they are unconverted prospects. We resolve the split using available Makesbridge data (company association, Hot List membership, Lead Score threshold) and set a custom field source_system__c = 'Makesbridge' on every record for audit. Email address is the dedupe key on Person insert; duplicate emails are flagged for manual resolution.

Makesbridge supports unlimited custom fields per Subscriber. We retrieve the full custom field schema via API and validate each field type against Nutshell's supported types (Text, Long Text, Currency, Date, Number). Field type differences are resolved during transform: date pickers become Nutshell Date fields, numeric scores become Number fields, and long-form text becomes Long Text. We pre-create all destination custom fields in Nutshell before the first record insert.

Tags applied to Makesbridge Subscribers export as individual tag strings per record. Each distinct tag becomes a Nutshell Tag attached to the corresponding Person or Lead. Tag membership is preserved as a static snapshot at migration time. Tag count per record migrates as-is; no tag hierarchy or folder structure is carried over because Makesbridge does not expose that metadata via API.

Makesbridge Lists (named audience groups) map to Nutshell Tags as the equivalent audience concept. The list membership snapshot at migration time becomes the initial tag membership in Nutshell. We flag which Nutshell Tags originated from Makesbridge Lists in the tag description field for the customer's admin to validate post-migration.

Makesbridge Campaigns (individual email sends and sequences) do not have a direct Nutshell equivalent, so campaign history migrates as Nutshell Tasks with the campaign name, send date, subject line, and aggregate metrics (open rate, click rate, send count) stored in the Task description. Each task is linked to the corresponding Person record. Only campaign-level aggregates are available; individual open/click activity is not accessible via Makesbridge API.

Makesbridge Hot Lists are high-priority subscriber groups surfaced by the lead scoring engine. Hot List membership migrates as a custom Number field (priority_score__c) set to 1 for Hot List members and 0 otherwise on the Person record. The customer can use this field to create Nutshell Views or automation triggers for priority follow-up.

Makesbridge computes per-subscriber lead scores based on behavior and data triggers. Current score values migrate as a custom Number field lead_score__c on the Nutshell Person record. Score thresholds and tier labels are documented in the migration artifact for the customer to recreate as Nutshell automation rules or view filters.

Makesbridge does not have a native Company object, but Subscribers may have a company_name field. If a company_name value exists on a Subscriber record, we create a Nutshell Company record first and link the Person to it via the Nutshell Company lookup. Custom fields on company_name carry over as Company-level custom fields.

Makesbridge user accounts (Owner/User assignments on Subscribers) map to Nutshell Users by email match. Any Makesbridge Owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Role and permission sets are preserved as a custom text field on the User record.

Makesbridge stores automation workflows in a text-based format without a documented export schema for re-import. We extract step sequences, delay settings, trigger conditions, and action types as structured text in a migration artifact document. The customer's admin uses this artifact to manually rebuild automation rules in Nutshell. This is not a code migration.