Migrate from RAYNET CRM to Twenty CRM

RAYNET Contacts map directly to Twenty People records. Standard fields (name, email, phone, address) map 1:1. RAYNET's lifecycle stage property maps to a custom select field in Twenty that we pre-create during schema setup. GPS coordinates derived from contact addresses for RAYNET Map Analysis transfer as two custom number fields (latitude, longitude) since Twenty has no native map analysis feature.

RAYNET Accounts map to Twenty Companies. The Account name becomes Company name, and contact address fields map to Twenty's company address fields. We migrate Account-Contact relationships by importing Companies first, then resolving the main contact lookup during People import using RAYNET's primary contact reference.

RAYNET Deals map to Twenty Opportunities with deal value, probability, owner, and estimated close date preserved. Pipeline stage names from RAYNET map to Twenty opportunity stage values that we configure before migration. Closed-won and closed-lost reasons from RAYNET custom fields become custom text fields on the Twenty Opportunity.

Each RAYNET pipeline (START/PROFESSIONAL: single; ENTERPRISE: multiple) becomes a Twenty opportunity stage configuration. Stage names, order, and probabilities extract from RAYNET's pipeline settings and map to Twenty stage values in Settings. If RAYNET uses multiple pipelines on ENTERPRISE, we create Twenty stage groups or use custom select fields to preserve the multi-pipeline structure.

RAYNET Activities map to Twenty Tasks (for calls and tasks) or Notes (for email body and meeting details). Call duration and disposition from RAYNET map to custom number and select fields on the Twenty Task. Meeting timestamps and attendee information map to Note body with structured content. Activity links to Contacts and Accounts preserve via Twenty's relation system.

Twenty does not have a native Sales Order object. We create a Twenty Custom Object named SalesOrder with fields for Subject, Final Price, Status, Estimated Costs, Delivery Date, and address fields. The object and all fields are pre-created in Twenty Settings before data import. We link SalesOrder to the parent Opportunity via Twenty's custom relationship field.

RAYNET Quotes (with validity dates and line-item pricing linked to Deals and Accounts) map to a Twenty Custom Object named Quote. Validity dates and pricing fields transfer to custom fields on the Quote object. Quote PDFs do not migrate as native files; we document the source Quote ID so the customer's admin can re-attach documents post-migration.

RAYNET Users map to Twenty Members. We match by email address. Any RAYNET Owner without a matching Twenty Member goes to a reconciliation queue for the customer to provision before record import resumes. Twenty's documentation explicitly requires users to exist before import because Owner references cannot map without a destination User ID.

RAYNET custom fields on Contacts, Accounts, Deals, and Activities extract via XLSX export and schema review. We create equivalent Twenty custom fields in Settings before any import. Field types map: RAYNET text to Twenty text, number to number, date to date, select to select, multi-select to multi-select. Multi-select picklist options must match exactly or the import rejects those values.

Files attached to RAYNET Contacts, Accounts, Deals, and Activities export via XLSX export with record cross-references. We do not migrate attachments directly through API because RAYNET's attachment storage format is not publicly documented. We re-upload attachments to Twenty using the source record's Twenty ID mapping, re-associated manually or via batch file upload with the cross-reference manifest.

RAYNET Tags on Contacts and Deals migrate as label arrays into a Twenty custom multi-select field. If the customer uses tags for content classification, we recommend a Twenty custom select field with tag values as options. The customer chooses tag strategy during scoping.