Migrate from Sales ERP to Infor CloudSuite Corporate

Salesforce Account records map to Infor CloudSuite Business Partner entities with BP Type = Customer (or Prospect). The Account Name becomes BP Name, Shipping Address maps to Ship-To address, and Billing Address maps to Bill-To address. Business Partner must be inserted before Contact and before any Order referencing that BP. Multi-site organizations with multiple Shipping Addresses in Salesforce become separate Address records linked to the same Business Partner.

Salesforce Contact records map to Infor CloudSuite Contact entities linked to a Business Partner. The Contact FirstName and LastName map to Contact Name fields, Email maps to Email Address, and Phone maps to Phone. Salesforce Contact roles on Accounts map to Contact Address roles in Infor. De-duplication is based on email match against existing Infor Contacts within the same Business Partner.

Salesforce Opportunity records map to Infor CloudSuite Sales Quote (pre-close) or Sales Order (post-close) entities. The Opportunity Name becomes Quote/Order Description. StageName maps to Order Status (Quote, Released, Shipped, Invoiced). CloseDate maps to Order Date or Required Date. Amount maps to Order Total with currency preserved. The mapping splits depends on whether the Opportunity is open (Quote) or closed-won (Sales Order) at migration time.

Salesforce Lead records map to Infor CloudSuite Prospect entities. Lead_Status maps to Prospect Status, and Lead_Score maps to a custom field. Converted Leads that have already been converted to Account and Contact in Salesforce map as Business Partner and Contact rather than Prospect. We apply the same split logic used in the Salesforce org to determine whether to import as Prospect or Business Partner.

Salesforce Order records map to Infor CloudSuite Sales Order with OrderNumber preserved as a custom field, Status maps to Order Status, and TotalAmount maps to Order Total. The Account-Order relationship maps via the Business Partner reference. Order items (OrderProducts) map to Sales Order Line records with Item Number, Quantity, and Unit Price.

Salesforce Contract records map to Infor CloudSuite Contract entities linked to a Business Partner. Contract Number, StartDate, EndDate, and Status migrate directly. Contract Line Items map to Contract Schedule lines if the destination configuration includes contract management. Renewal terms and special pricing conditions require custom field mapping.

Salesforce Product2 records map to Infor CloudSuite Item master records. Product Name becomes Item Description, ProductCode becomes Item Number (with validation against Infor's alphanumeric format), and IsActive maps to Item Status. Product families map to Infor Product Groups. Price Book Entries with standard prices become Infor Sales Price records linked to the Item.

Salesforce Opportunity Product (Line Item) records map to Infor CloudSuite Sales Order Line records. We resolve the Product2 reference to the Item Number, the PricebookEntry to the Sales Price, and the parent Opportunity to the Sales Order. Quantity, UnitPrice, and TotalPrice migrate directly with currency handling applied.

Salesforce User records map to Infor CloudSuite User entities by email match. OwnerId references on Account, Contact, Opportunity, and Order resolve through this mapping. We flag any Salesforce Owner without a matching Infor User for admin provisioning before record migration. Active vs inactive status is preserved. Role and Profile assignments do not have a direct Infor equivalent and are documented for manual assignment post-migration.

Salesforce custom objects require a schema mapping assessment before migration. Simple custom objects with standard field types (text, number, date, picklist) map to Infor CloudSuite extended data structures or custom fields on the equivalent standard entity. Complex custom objects with cross-object lookups may require redesign as separate tables with explicit join fields. We cannot apply custom formulas or validation rules from Salesforce to Infor; these are documented for manual configuration post-migration.

Salesforce Attachments on Account, Contact, Opportunity, and Order migrate to Infor Document Management (IDM) linked to the corresponding Business Partner, Contact, Sales Quote, or Sales Order. Each attachment is stored as a document record with the original filename, content type, and binary content. Notes migrate as text documents in IDM with the same parent reference. Multi-attachment-per-record scenarios are handled as separate IDM document records with a sequence or category field to preserve original ordering.

Salesforce Cases map to Infor CloudSuite Service Management tickets if the destination configuration includes the service module. Case Number becomes Ticket Number, Status maps to Ticket Status, and Priority maps to Ticket Priority. If the service module is not in scope, Cases map to Project Task records or are documented as requiring the Service Management module activation. Case Comments migrate as Notes attached to the Ticket.