Migrate from Infor CloudSuite Customer Relationship Management (CRM) to Twenty CRM

Infor CRM Accounts (the Customers form) map directly to Twenty CRM Company records. The Account holds company-level data including SIC code, revenue, employee count, territory assignments, and the CRM tab fields. We extract via Infor's group export with SpeedSearch chunking to avoid UI timeouts on large account lists. Company becomes the top-level parent record; it must load before any Contact or Opportunity records that reference it. The Account name field maps directly to Company name; domain or website maps to the URL field if populated in Infor.

Infor CRM Sales Contacts link to Accounts via the Account foreign key and store the individual contact's name, role, phone, and email. We resolve the AccountId reference at migration time and attach the Person record to the corresponding Twenty Company. The Outlook integration creates duplicates in Infor; we deduplicate on email address and name matching before loading into Twenty. Any contact with an email matching an existing record in Twenty goes to a reconciliation queue for admin review.

Infor CRM Opportunities track deal stage, value, probability, and close date and link to Accounts and Owners. They map directly to Twenty Opportunity records. The Infor Opportunity stage value maps to a Twenty Opportunity stage via a stage-mapping spreadsheet created during scoping. Opportunity value maps to the amount field; close date maps directly. OwnerId resolves via email match against the Twenty User table.

Infor CRM Leads are captured via the Leads form, store status, source, and owner, and can be converted to Opportunities. We migrate Lead records with status, source, owner, and any custom fields preserved. If the destination Twenty workspace uses Opportunities for all pipeline records rather than a separate Lead object, Leads with status below a configurable threshold (e.g., unqualified) are imported as Opportunity records with a pre-conversion stage flag.

Infor CRM Sales Forecasts aggregate Opportunities into Sales Periods — named date-range constructs that define fiscal or forecast period structure. This is not a standard date field; it is a distinct schema form. We decompose each Sales Period into its start and end date boundaries and apply those date ranges to the migrated Opportunity close dates or forecast date fields in Twenty. The forecast total per rep and territory maps to a custom number field on the Opportunity or a separate Forecast record if Twenty is configured with a dedicated forecast object. The mapping is explicit and documented in the field mapping spreadsheet before any data loads.

Infor CRM Activities and Events track calls, meetings, notes, and tasks with due dates and owner assignments, stored against Contacts or Opportunities. We map Activity type (Call, Meeting, Note, Task) to the corresponding Twenty record type. The activity description, date, and owner migrate. Call disposition and duration from Infor map to custom fields on the Twenty Task record. Activities attached to a Contact or Opportunity link to the migrated Person or Opportunity record via the Twenty relationship API.

Infor CRM Campaigns store campaign type, status, start/end dates, and budget. Campaign Items link products or contacts to a campaign. We migrate Campaign records as a custom object in Twenty, preserving campaign type, status, start date, end date, and budget. Campaign Items map to a Campaign Member custom relationship linking contacts (People records) to the campaign custom object. If Twenty's standard objects support campaigns, we map to the standard equivalent.

Infor CRM's ticketing system stores support cases with status, priority, assigned agent, and conversation history. We map ticket records to Twenty Task records with a case-type designation (custom field or tag) to distinguish them from sales activities. Ticket status maps to a set of Task status values. Conversation history from the ticket migrates as Note records linked to the Task. Multi-line ticket conversations flatten to a single note per exchange or a series of timestamped notes preserving the thread order.

Infor CRM supports custom fields on Accounts, Contacts, Opportunities, and Tickets using Infor-specific field types (picklists, dates, lookups). We inventory all custom fields during scoping, classify each by Infor field type, and map to the corresponding Twenty field type. Picklists in Infor become picklist or multi-select fields in Twenty. Infor date fields map directly to Twenty date fields. Infor lookup fields (references to related records) map to Twenty relationship fields where supported or to text fields holding the referenced record name as a fallback. Custom field mapping is documented field-by-field in the spreadsheet before migration begins.

Infor CRM Users serve as record Owners and are linked to Territories. We map Users to Twenty workspace accounts by email match. Any Infor User without a matching Twenty User is held in a reconciliation queue; the customer's admin provisions the corresponding account in Twenty before record import resumes. OwnerId references on Opportunities, Activities, and Tickets are resolved at migration time using the validated User mapping table.

Territory assignments in Infor CRM map sales reps to geographic or account-based regions. Quotas are set per rep per territory per period. We migrate the territory structure as a custom picklist field on the Opportunity or Person record in Twenty, and quota values as a custom number field. Twenty does not have a native territory management module; the territory-quota structure maps to workspace-level custom fields that sales management configures in Twenty's field editor post-migration.

Attachments stored against Contacts, Accounts, Opportunities, and Tickets in Infor CRM export to a file store with the attachment filename and linked record reference. We attach each file to the corresponding migrated record in Twenty via the Twenty API file attachment endpoint. Email attachments from the Outlook integration export similarly with the parent email or contact reference preserved. Large binary attachments (over 25 MB) require chunked upload handling via the Twenty API.