Migrate from Marketing Star to Twenty CRM

Marketing Star Contacts map directly to Twenty Person records. The contact's first name and last name split into Person.name.firstName and Person.name.lastName. Email maps to Person.emails.primary.rawEmail and Person.emails.primary.email; mobile phone maps to Person.phone.rawPhone with phoneType = mobile. We validate every record during profiling: Marketing Star requires at least email or mobile phone on every contact, so we flag records missing both and ask the customer to exclude, enrich, or suppress them before migration. List membership migrates as tag assignments on the Person record. Original Lifecycle Stage or engagement source migrates as a custom text field for audit.

Marketing Star Companies map to Twenty Company records. The company domain becomes Company.domainName and the company name maps to Company.name. Company size (employee count), industry, and address fields map to their Twenty equivalents. If the customer uses company records primarily for B2B segmentation rather than standalone entities, we may merge them as CompanyLinks on the Person record instead, depending on the customer's data model preference.

Marketing Star Lists are the primary segmentation unit and may contain up to 500,000 records on Ultimate tier. We export list membership as Person-to-tag associations in Twenty, creating a tag for each list name. If the customer has fewer than 50 lists, we create individual tags; if they have more, we group them under a segment namespace to avoid tag proliferation. The list-to-tag mapping is documented in the migration manifest for the customer's admin to validate post-migration.

Marketing Star Campaigns track multichannel sends (email, SMS, QR triggers). Campaign name, send dates, and high-level metrics (open rate, click rate, delivery count) migrate as a Twenty Opportunity record with custom fields capturing the marketing campaign context. The Opportunity links to the Person records that were targeted, maintaining the campaign-to-contact relationship. Automation logic within campaigns requires remapping in the destination as there is no direct equivalent in Twenty's workflow model.

Marketing Star Forms capture leads and populate contact fields. Form structure and field-to-property mappings are exportable as a JSON schema. We translate form submissions into Note records attached to the Person record in Twenty, capturing submission timestamp, form name, and field values as structured note body text. The customer should confirm which form fields map to standard Person fields versus remaining as note content.

Landing pages are available only on Marketing Star Ultimate tier ($500/month). We export page content, URL redirects, and form embed configurations as a static content package. Twenty CRM does not include a native landing page builder; the customer rebuilds pages in a dedicated landing page tool or as static assets hosted elsewhere. We document the original URLs and redirect targets for the customer's marketing team to implement as301 redirects in their hosting environment.

SMS contacts in Marketing Star are distinguished by mobile phone number with a separate opt-in flag. We preserve mobile opt-in status in a custom boolean field sms_consent__c on the Person record. The mobile phone number itself migrates to Person.phone.rawPhone with phoneType = mobile as part of the Contact mapping. If the customer uses SMS consent tracking for regulatory compliance (TCPA, GDPR), we ensure the consent timestamp and source are preserved in custom fields.

QR codes in Marketing Star are tied to campaigns or forms and track physical-to-digital attribution. QR code metadata (code identifier, redirect URL, campaign association) migrates as a Note on the related Person or Opportunity record in Twenty. The tracking URLs require recreation in the destination's analytics or campaign attribution setup; we document the original QR-to-URL mapping for the customer to re-establish in their analytics platform.

Marketing Star Automation Workflows are not migrated as executable code. We export the workflow logic (triggers, conditions, delay steps, action sequences) as a structured written inventory. Each workflow entry includes the original trigger type, all conditional branches, delay durations, and CRM actions (field updates, list assignments, email triggers). The customer uses this document to rebuild equivalent logic in Twenty's preferred automation environment. Twenty has no native workflow engine, so workflows must be rebuilt in external tools or custom code.

Marketing Star email engagement history migrates to Twenty TimelineEntry records attached to the Person. Each entry captures direction (inbound/outbound), subject, body content, timestamp, and open/click events as sub-entries. We resolve the Person record by email address lookup before inserting. For large engagement volumes (over 50,000 email records), we use the Twenty REST API with pagination and batch chunking to avoid timeouts.

Marketing Star call engagements migrate to Twenty TimelineEntry records with call direction, disposition, duration (in seconds), and recording URL preserved in custom fields. Activity timestamp migrates as the TimelineEntry date. We resolve the Person record by phone number or email lookup before inserting. Call disposition codes map to a custom picklist field on the TimelineEntry.

Marketing Star meeting engagements migrate to Twenty CalendarEvent records attached to the Person. Event title, start time, end time, location, and attendee list preserve. Attendee mapping creates CalendarEventParticipant records for each invitee resolved to a Person record by email. We set CalendarEvent.visibility to the Twenty equivalent of the original meeting visibility setting.