Migrate from Makesbridge to Twenty CRM

Makesbridge Subscribers map to Twenty People records. Standard fields (first name, last name, email, phone) migrate directly. Custom field values on each Subscriber transfer to custom fields on the People record. The migration extracts Subscribers via Makesbridge's individual API operations (no bulk endpoint available), which extends the extraction phase for large subscriber lists. We deduplicate on email address before import to avoid duplicate People records in Twenty.

Makesbridge Subscribers can carry a company name field. Where a company name is present, we create a corresponding Company record in Twenty and link it to the People record via the main contact or work group relationship. Where no company name is present, the Subscriber becomes a standalone People record without a Company link. Company deduplication uses domain-based matching on email addresses when available.

Makesbridge Deals (if present in the customer's data model) map to Twenty Opportunities. We map deal stage to Twenty pipeline stage, amount to amount, close date to close date, and owner to the assigned Twenty workspace member. Deal owner resolution requires matching the Makesbridge owner email to a provisioned Twenty user before import.

Makesbridge Lists are named audience groups containing Subscribers. We export the list structure and member assignments, then map each List to a corresponding Tag applied to the relevant People records in Twenty. If the customer maintains a large number of Lists with distinct purposes (e.g., industry segmentation, lifecycle stage lists), we discuss whether to map them as Tags or as separate workspace views during scoping.

Makesbridge Segments are defined by dynamic rules combining behavior triggers and demographic conditions. The segment rule definitions themselves are not accessible via the Makesbridge API. We export the evaluated Subscriber set at migration time as a static list and apply a corresponding Tag to each People record in Twenty. Customers who depend on dynamic segment rules for ongoing segmentation must plan to recreate those rules in Twenty using the migrated subscriber data as a reference starting point.

Makesbridge Hot Lists are high-priority subscriber groups surfaced by the lead scoring engine. We export Hot List memberships and assign a priority indicator on each migrated People record. The migration delivers this as a Tag (e.g., 'Hot List — Q3 Priority') or as a custom checkbox field depending on the customer's preference, confirmed during scoping. The numeric lead score itself migrates as a custom number field on the People record.

Makesbridge computes lead scores per Subscriber based on behavior and data triggers. We export the current score value as a numeric custom field on each People record at migration time. Because Twenty does not have a native lead scoring engine, the migrated score is a static snapshot reflecting the value at cutover. Future scoring logic must be rebuilt using Twenty's Workflow builder or a third-party scoring integration.

Makesbridge Campaigns represent individual email sends or nurture sequences. Campaign metadata (name, subject line, send date, aggregate open rate, click rate, send count) migrates as structured text in a Note attached to the relevant People records. The HTML content of individual emails is preserved and delivered as a file artifact for reference. Campaign-level aggregates provide historical context for reporting even though granular per-email open events are not accessible via Makesbridge's API.

Makesbridge supports unlimited custom fields per Subscriber. We retrieve the full custom field schema via the Makesbridge API and map each field name and type to a corresponding Twenty custom field. Field type differences require validation: Makesbridge text fields can map to Twenty text fields; date fields map to date fields; numeric fields map to number fields. If a Makesbridge custom field uses a type that Twenty does not support natively, we discuss alternatives (multi-select text, date stored as ISO string) during field mapping.

Tags applied to Makesbridge Subscribers export as individual tag strings per contact and map directly to Twenty Tags on the People record. Tag strings are preserved as-is; no transformation is applied unless the customer requests normalization during scoping. Tags used for multiple purposes (industry, lifecycle stage, team assignment) remain as separate tag entries on each record.

Makesbridge Workflows define automation sequences with triggers, conditions, delays, and CRM actions. The workflow logic is stored in a text-based format without a documented export schema, so workflows cannot be re-imported directly into Twenty. We extract the step sequence, trigger conditions, delay settings, and action list as a structured migration artifact document. Twenty's admin uses this document to rebuild each workflow in Twenty's Workflow builder. The rebuild is outside standard migration scope.