Migrate your Infor CloudSuite Customer Relationship Management (CRM) data

Accounts are the top-level organizational records in Infor CRM, holding company-level data including SIC code, revenue, employee count, and territory assignments. The CRM tab on the Customers form maintains this data. We migrate Accounts as the primary parent object and preserve the cross-reference to Sales Contacts via the contact's AccountId foreign key.

Sales Contacts are linked to Accounts and store the individual contact's name, role, phone, and email. Outlook import/export does not sync — it duplicates records. We handle deduplication during migration scoping and map the cross-reference to the parent Account using the AccountId lookup.

Opportunities track deal stage, value, probability, and close date. They link to Accounts and can attach to Prospects or Customers. We preserve the stage, value, probability, owner assignment, and the Account lookups. Custom Opportunity fields are mapped field-by-field to the destination.

Leads are captured via the Leads form and can be converted to Opportunities. We migrate the Lead record including status, source, and owner. If the destination has a separate Lead object (like Salesforce), we land them there; if not, we merge into Contacts and preserve lead source as a custom property.

Activities and Events track calls, meetings, notes, and tasks with due dates and owner assignments. Infor stores them against Contacts or Opportunities. We map the Activity type, description, date, and linked Contact/Opportunity ID. Multi-day Events require date-range mapping.

Sales Forecasts aggregate Opportunities into forecast periods. The Sales Periods form defines period date ranges. We map forecast totals and the period schema — these are date-window constructs that require explicit mapping to the destination CRM's fiscal period or forecast group.

Campaigns store campaign type, status, start/end dates, and budget. Campaign Items link products or contacts to a campaign. We migrate Campaigns and Campaign Items preserving the campaign association. Campaign status values map to the destination's lifecycle stage equivalent.

Products and price lists are managed in the CRM for quoting. The Price List form stores pricing tiers. We migrate the product catalog and associated price schedules. Complex tiered pricing requires value-level mapping to the destination's pricing model.

Quotes and Orders in Infor CRM are linked to Opportunities and Accounts. The Quote holds products, prices, and discounts. We migrate Quote headers and line items with Opportunity and Account lookups preserved where possible. Historical orders are migrated as read-only records in most destination CRMs.

Infor CRM's ticketing system stores support cases with status, priority, assigned agent, and conversation history. We map the ticket record, linked Account/Contact, status, and notes. Multi-line ticket comments may require flattening into a single notes field in the destination.

Infor CRM supports custom fields on Accounts, Contacts, Opportunities, and Tickets. These are user-defined properties with Infor-specific field types (picklists, dates, lookups). We inventory all custom fields during the discovery phase and map each to the destination's equivalent custom property, flagging any Infor-specific picklist values that require value translation.

Attachments can be stored against Contacts, Accounts, Opportunities, and Tickets. The Outlook integration can attach emails. We export attachments to a file store and create links in the destination system. Attachment metadata (filename, type, date, linked object) is preserved in the migration manifest.

Territory assignments map sales reps to geographic or account-based regions. Quotas are set per rep per territory per period. We migrate the territory structure and quota values, noting that the destination CRM's quota management may not have a direct equivalent — quota records may become custom objects or Opportunities.

Users in Infor CRM serve as record Owners and are linked to Territories. We map Users to the destination CRM's user accounts, preserving the Owner relationship on Opportunities, Tickets, and Activities. Inactive users are archived rather than deleted to preserve historical ownership.

Infor CRM uses Groups to segment records — a Group is a saved query result with a name. We migrate the Group definition (the query criteria) and apply it in the destination, or replicate the resulting record list. Groups referencing large datasets require chunked processing.