Migrate from Infor CloudSuite Customer Relationship Management (CRM) to Microsoft Dynamics 365 Sales

Infor CRM Accounts map directly to Microsoft Dynamics 365 Sales Account. The Account is the top-level organizational record holding company-level data including SIC code, revenue, employee count, and territory assignments. We load Accounts first in every migration because all downstream objects (Contacts, Opportunities, Activities) carry foreign keys back to the Account. Infor's Account-SIC-Code and territory assignments migrate to custom fields if the destination Dynamics 365 org does not have those standard fields configured.

Infor CRM Sales Contacts map to Microsoft Dynamics 365 Sales Contact with the AccountId lookup resolved to the parent Account created in the first phase. Infor's Outlook import/export does not perform true sync; it creates duplicate records on both sides. We deduplicate Infor Contacts on email address and name matching before inserting into Dynamics 365 to avoid landing duplicate Contact records. Any Contact without a parent Account is held in a reconciliation queue.

Infor CRM Opportunities map to Microsoft Dynamics 365 Sales Opportunity with the AccountId lookup resolved to the parent Account and the OwnerId lookup resolved to the mapped Dynamics 365 User. Stage names, probability percentages, close dates, and estimated values migrate directly. Infor Opportunity linking to Sales Periods requires a cross-reference table in the mapping spreadsheet. We configure the Opportunity Record Type and Sales Process in Dynamics 365 before migration to match Infor's pipeline and stage schema.

Infor CRM Leads map to Microsoft Dynamics 365 Sales Lead. Lead status, source, owner, and custom fields migrate directly. We preserve the Infor Lead score (if present) in a custom field on the Dynamics 365 Lead. If the destination uses Leads for marketing qualification before conversion to Contacts and Opportunities, we apply the customer's lead-status rules during the import. The Lead status values are mapped to the configured Lead Status picklist in the destination org.

Infor CRM Activities attach to Contacts or Opportunities and include Tasks, Events, Calls, and Notes. We split these into the corresponding Microsoft Dynamics 365 Sales objects: Tasks for action items and notes, Events for calendar entries with StartDateTime and EndDateTime, and EmailMessage for email history. The WhoId on the Dynamics 365 record points to the converted Contact or Lead; the WhatId points to the related Opportunity or Account. Activity timestamps are preserved as ActivityDate on Task and StartDateTime on Event.

Infor CRM organizes Sales Forecasts into Sales Periods, which are named date-range schema constructs not standard date fields. We decompose each Sales Period into start and end date boundaries and map the forecast totals to Opportunity fields (estimated revenue, close date) and to a custom Forecast Period object. The customer's admin configures the Dynamics 365 Forecasting workspace to match the Infor Sales Period structure after migration. Complex multi-level forecast hierarchies may require a custom solution beyond standard Dynamics 365 Forecasting.

Infor CRM Campaigns store type, status, start/end dates, and budget. Campaign Items link products or contacts to a campaign. Both migrate as a unit to Microsoft Dynamics 365 Sales Campaign and CampaignItem. CampaignItem links are resolved by Contact email during import. Campaign budget and status map directly to the Dynamics 365 Campaign fields.

Infor CRM Products and price lists are managed in the CRM for quoting. We migrate the product catalog and associated price schedules to Microsoft Dynamics 365 Sales Product2 records with Standard Price Book entries. Complex tiered pricing requires validation against the destination Pricebook2 structure and may need a custom pricing solution beyond standard Dynamics 365 product pricing.

Infor CRM Quotes attached to Opportunities map to Microsoft Dynamics 365 Sales Quote records linked to the Opportunity. Quote headers and line items migrate with Opportunity and Account lookups resolved. If the destination does not have the Quote object enabled, Quotes migrate as Opportunity product lines with a custom Quote Status field capturing the original quote state.

Infor CRM ticketing stores support cases with status, priority, assigned agent, and conversation history linked to the Account and Contact. We migrate Ticket records to Microsoft Dynamics 365 Sales Case, resolving AccountId and ContactId lookups. Multi-line ticket conversations migrate as Case comments or EmailMessage records attached to the Case. Case Record Types and Status values are configured in the destination org to match Infor's ticket stage schema.

Infor CRM supports user-defined custom fields on Accounts, Contacts, Opportunities, and Tickets with Infor-specific field types (picklists, dates, lookups). We inventory all custom fields during discovery, map them to typed Dynamics 365 custom fields, and pre-create the destination schema in the Sandbox before any data loads. Infor picklist values map to Dynamics 365 picklist or multi-select picklist values with a mapping table for each field.

Infor CRM stores attachments against Contacts, Accounts, Opportunities, and Tickets. We export attachments to a file store, then migrate them to SharePoint Online or Dynamics 365 native file storage. We create SharePoint Document Location records or Note records with file links on the parent Dynamics 365 Account, Contact, or Opportunity. Original file names and Infor metadata are preserved in the file description field.

Infor CRM territories assign sales reps to geographic or account-based regions with quota values per rep per territory per period. Microsoft Dynamics 365 Sales does not have a direct Territory object at all tiers. We create a custom Territory object with the hierarchy structure and map Infor quota values to custom fields. The customer's admin rebuilds the territory assignment UI in the Dynamics 365 Forecasting workspace. Complex multi-level quota hierarchies may require a custom solution.

Infor CRM Users serve as record Owners and link to Territories. We extract all distinct Users referenced on migrating records and match by email against the Dynamics 365 User table. Any Infor User without a matching Dynamics 365 User is placed in a reconciliation queue. The customer's admin provisions missing Users before the production migration phase begins, as OwnerId references are required on standard objects.

Infor CRM Groups are saved query results that segment records by defined criteria. Microsoft Dynamics 365 Sales does not have a direct equivalent to Infor's Group concept. We migrate the Group name and document the query criteria in the mapping spreadsheet. The customer's admin recreates each Group as an Advanced Find saved view or exports the resulting record set as a manual list in Dynamics 365. If the customer has more than 20 Groups, we flag this as a separate cleanup engagement.