Migrate from Sales Infinite to Twenty CRM

Sales Infinite Contact records map directly to Twenty CRM Person records. The mapping covers firstName, lastName, email, phone, and address fields. Owner assignment in Sales Infinite maps to a Twenty CRM workspace User resolved by email match. Custom properties on Contact records are flagged during schema discovery and mapped to custom fields pre-created in Twenty CRM. Records with missing required fields (such as an empty lastName) are held in a remediation queue rather than imported with silent failures.

Sales Infinite Account records map 1:1 to Twenty CRM Company records. Industry, annual revenue, type, website, and address fields translate directly. The Account's name maps to Company name. Any custom Account properties exceeding the standard field set are pre-created as Company custom fields in Twenty before migration. Company is imported before Person so that the Person-to-Company relationship lookup is satisfied at insert time.

Sales Infinite Opportunity records map to Twenty CRM Opportunity with amount, closeDate, and stageName preserved. Pipeline assignment from Sales Infinite maps to a Twenty CRM pipeline that we configure during the schema phase. Stage names that differ between the two platforms (for example, Sales Infinite's internal stage labels versus Twenty's default set) are mapped explicitly using a stage translation table built during discovery.

Sales Infinite Lead records map to Twenty CRM Person records with a custom field original_record_type__c set to 'Lead' to preserve the source classification. This approach is used when the destination lacks a separate Lead object or when the customer's sales process does not require a distinct Lead-to-Contact conversion step. Lead_Status and lead score values from Sales Infinite migrate to custom Person fields so that the customer's admin can segment and act on the original lead data post-migration.

Sales Infinite pipeline stages are extracted during discovery as a labeled list with probability percentages. We configure each stage in Twenty CRM's pipeline builder before Opportunity records migrate. Closed-Lost and Closed-Won labels map from Sales Infinite to Twenty's equivalent stage values. If Sales Infinite has stages with no Twenty equivalent, we create custom stage values and document the gap for the customer's admin to name appropriately.

Sales Infinite pipeline configuration (stage ordering, stage labels, probability weights) migrates as Twenty CRM pipeline setup. Each Sales Infinite pipeline becomes a separate Twenty CRM pipeline. Stage probability percentages are entered manually into Twenty's pipeline configuration. This step is a configuration-only migration (no records) that we complete before Opportunity record import begins.

Sales Infinite call activity records migrate as Twenty CRM Tasks with the task type set to 'call'. Call duration, disposition, and any notes from Sales Infinite map to custom Task fields in Twenty. The parent Person or Opportunity reference is resolved by email match or Opportunity name match before insert. Activity timestamps are preserved to maintain the chronological engagement timeline in Twenty.

Sales Infinite email engagement records migrate as Twenty CRM Tasks with task type set to 'email'. The email body and subject line transfer as the task description. Recipients and CC addresses are preserved in a custom task field. The parent Person or Opportunity lookup is resolved at migration time using the email address or Opportunity association stored in Sales Infinite.

Sales Infinite meeting records migrate as Twenty CRM Tasks with task type set to 'meeting'. Start time, end time, location, and attendee list transfer as task fields. The meeting title becomes the task subject. Each attendee email is matched to a Person record in Twenty CRM and linked via the task's person association. If the attendee is not yet a migrated Person record, the attendee email is stored in a custom attendees field for later reconciliation.

Sales Infinite task activity records map to Twenty CRM Task with Status, Priority, dueDate, and description preserved. Task assignments in Sales Infinite (owner or team) are resolved via email match to Twenty CRM Users. Completed status and completion timestamps carry over. Open tasks are imported as open in Twenty so that no in-flight follow-up items are lost during migration.

Sales Infinite Notes migrate as Twenty CRM Note records linked to the parent Person, Company, or Opportunity. Note body content transfers as rich text. Notes with file attachments download via the Sales Infinite API and re-upload to Twenty CRM linked to the same parent record. Large attachment sets increase extraction time and are handled in batches to respect API rate limits on both platforms.

Sales Infinite custom objects migrate to Twenty CRM custom objects of equivalent name and structure. We pre-create the destination custom object schema in Twenty CRM, including all custom fields and their types, before any custom object records are imported. Lookup relationships from custom objects to standard objects (Person, Company, Opportunity) are resolved at migration time using the referenced record's primary identifier. Custom object naming follows the customer's established naming convention and is preserved in Twenty's schema.