Migrate from Net-Results to Twenty CRM

Net-Results Contact records map to Twenty Person records. Standard fields (first name, last name, email, phone, address) migrate directly. Lifecycle stage metadata from Net-Results becomes a custom text field person_lifecycle_stage__c on the Person record. We deduplicate on email address against any existing Twenty Persons at migration time. If the Net-Results Contact has a related Company, we resolve the Organization lookup before Contact insert.

Net-Results Company records map to Twenty Organization records. The company_name and domain fields become Organization name and website. Any custom company properties require explicit field mapping against Twenty's Organization schema during discovery. Organization records are created before the Contact import so that the Person-Organization lookup is satisfied at the moment of Person insert.

Net-Results Campaigns do not have a direct equivalent in Twenty CRM. We map campaign name and status to a Tag on Person records and optionally to an Opportunity with campaign-type naming. Campaign dates and type metadata migrate as Opportunity custom fields or as a note on the primary Person if no deal is associated. The customer chooses the campaign strategy during scoping.

Individual Net-Results send events (opens, clicks, bounces) are activity-level records. We preserve send timestamps, open/click rates, and bounce codes as Task records in Twenty linked to the Person. Twenty does not have a native send-event object, so email send history lands as a structured Task with custom fields capturing the campaign name, send date, open count, click count, and bounce status. Activity timeline ordering is preserved by setting the Task due date to the original Net-Results send timestamp.

Net-Results templates use a drag-and-drop HTML structure that does not render identically in other platforms. We export template HTML and image asset references as a static asset package. Because Twenty CRM has no native email template builder, the customer imports the HTML into their preferred email platform (Mailchimp, SendGrid, or similar) and links the resulting campaign back to Twenty Persons via Tag or Opportunity. We flag all templates for manual review and advise a send preview before launching imported assets.

Net-Results workflow logic does not export as a portable artifact. We capture the workflow name, associated contact count, and step-count metadata for every active workflow during discovery. We deliver a written Workflow Inventory document listing each Net-Results workflow with its trigger type, conditions, actions, and a recommended manual rebuild approach in Twenty using Tasks and Opportunity follow-ups. The customer's admin rebuilds workflows post-migration; this is outside standard migration scope.

Net-Results suppression records (hard bounces, unsubscribes, manual suppressions) export as a list of email addresses. We apply this as a post-load cleanup pass against Twenty Persons, setting the opt-out flag and writing a suppression timestamp to a custom field suppression_date__c. If Twenty already has existing Person records with opt-out status, we deduplicate against them to avoid false opt-out flags on valid active contacts. The suppression pass runs after the primary Person import to ensure all records are present.

Net-Results contact custom fields require explicit field-by-field mapping against Twenty's Person schema during discovery. Text fields map to text, date fields to date, pick lists to select, numeric fields to number. Lookup fields pointing to other Net-Results objects require a relationship strategy decision during scoping before schema creation in Twenty. We pre-create all custom fields in Twenty via the API before any data import to avoid type-mismatch rejections.

Net-Results company custom fields map to Twenty Organization custom fields using the same type-mapping logic as contact custom fields. Any pick-list values in Net-Results must be pre-created as valid select options in Twenty before import to avoid field validation errors.

Net-Results custom objects (defined with standard fields like Created By, Created Date, Id, and custom fields of type Date, DateTime, Lookup, Number, Pick List, Text, Website) require a scoping decision: whether the custom object maps to a Twenty Organization, to an Opportunity with custom fields, or to a separate custom table via Twenty's REST API. We inventory all custom objects during discovery, map their relationships to Net-Results Contacts and Companies, and pre-create the target schema before import. Lookup fields referencing Net-Results Contacts resolve to the corresponding Twenty Person ID at migration time.