Migrate from RSoft CRM to Twenty CRM

RSoft Contacts map to Twenty Persons. We map name fields, email, phone, address, lifecycle stage, and owner. RSoft's custom contact properties above the 5-field tier limit require manual review before import — any field exceeding the destination's plan limit is flagged and the customer decides which fields to create in Twenty before the migration begins. The Person.displayName is constructed from firstName and lastName if available; otherwise the full contact name string is used.

RSoft Leads map to Twenty Persons with a lead status marker. We extract Lead source, status, score, assigned owner, and associated activities. RSoft's Lead-to-Contact conversion record is preserved as a Person record with a conversion_date field we add as a custom field. If Twenty's workspace uses the opportunities feature, leads that have moved to a deal stage may alternatively map to an Opportunity linked to the Person.

RSoft Company records map directly to Twenty Company records. We map company name, industry, size, address, and owner. The Company-to-Person relationship is preserved by sequencing Companies first in the migration load order so that the Company record exists before any linked Person record is created in Twenty.

RSoft Deals map to Twenty Opportunities. We map deal amount, probability, expected close date, owner, and pipeline stage. RSoft uses a drag-and-drop pipeline builder allowing multiple pipelines; each RSoft pipeline maps to a Twenty pipeline configured before migration. Closed-Won and Closed-Lost reasons from RSoft custom fields migrate as Opportunity custom fields in Twenty.

RSoft custom stage names and probabilities map to Twenty pipeline stages. We extract the stage name, position, probability, and any stage-specific automation triggers and document them as Twenty stage configuration notes. Stage reordering is preserved by setting the sortOrder field in Twenty during pipeline setup.

Activities logged against Contacts, Leads, or Deals migrate as Tasks in Twenty. Call logs from IVR are flagged as a gap because RSoft stores IVR call recordings in a separate module not included in CSV export — we identify the count and total duration of orphaned IVR call records during scoping and offer a separate file-transfer approach if the customer wants to preserve audio files. Standard call and email log entries migrate as Tasks with the activity type preserved in a custom field.

RSoft Tickets migrate as Tasks in Twenty, with ticket status and priority mapped to custom task fields. RSoft's Ticket Management processes requests from email, online, phone, chat, and social media — the source channel is preserved in a custom field for audit. If Twenty's workspace uses a custom ticket object, we configure it during the schema design phase before import.

RSoft caps custom fields at 5 on Standard and Advanced plans. Any custom fields beyond that limit must be reviewed with the customer before import because they will be absent from the CSV export unless the customer is on the Customised plan. We audit the RSoft plan tier during discovery, list every custom field name and data type, and configure matching custom fields in Twenty before migration begins. Fields that exceed the destination plan's limits are flagged with a cost estimate for the appropriate Twenty plan tier.

RSoft does not expose document attachments via CSV export. Files linked to Contacts, Deals, or Tickets must be migrated separately via direct file transfer, not inline with record migration. We extract the list of attachment names and parent record IDs from the customer during discovery, bulk-transfer the files to a shared location, and attach them to the correct records in Twenty after the record migration completes using Twenty's file attachment API.

Tags on Contacts, Leads, and Deals export via CSV and map as Tags in Twenty. We deduplicate tags during import and preserve the association with the parent record (Person, Company, or Opportunity) using Twenty's tag API. Tags used for lead scoring in RSoft are preserved as tag values rather than converted to a numeric score field unless the customer requests the transformation.

RSoft user accounts map to WorkspaceMember records in Twenty. We extract the full user roster from RSoft and map each to a corresponding Twenty workspace member by email match. Orphaned owner references — records in RSoft assigned to a user who will not have an account in Twenty — are flagged in a reconciliation queue before migration. The customer's admin provisions any missing workspace members before record import begins.