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

Infor CRM Accounts map directly to Nutshell Companies. The Account Name becomes the Company name, and the CRM tab fields (SIC code, revenue, employee count, territory assignments) map to Nutshell custom fields since Nutshell's standard Company fields are limited to name, website, phone, address, and industry. Territory assignments from Infor have no native Nutshell equivalent; we map them to a custom Company field called Territory__c as a text picklist. Account owner maps to the Nutshell user assigned to the Company record.

Infor CRM Sales Contacts map to Nutshell People. We apply email-based deduplication before inserting because Infor's Outlook export creates duplicate contacts when a record already exists in Outlook. The deduplication key is email address plus name match. Phone, email, role/title, and address fields map directly. The link between Contact and Account (Infor's foreign key) maps to the Nutshell Person's Company association. Any Sales Contact without a valid Account becomes a standalone Person record in Nutshell.

Infor CRM Opportunities map to Nutshell Deals. Stage name maps to Nutshell pipeline stage, deal value maps to amount, probability maps to the probability percentage if the Nutshell plan supports it, and close date maps directly. Owner assignment resolves via email match to a Nutshell User. The Opportunity-to-Account lookup is preserved as the Deal's Company association in Nutshell. The Opportunity-to-Sales-Period lookup is decomposed: we extract the Sales Period start and end dates and apply the close date as the Deal's close date, noting the original Sales Period in a custom field.

Infor CRM Leads map directly to Nutshell Leads. Status, source, owner, and all standard fields transfer. Infor's Lead conversion process (converting a Lead to an Account/Contact/Opportunity) has no direct equivalent in Nutshell's simpler data model; if the customer used Infor's lead conversion before migration, the resulting Account and Contact records are already created and migrate as described above.

Infor CRM Activities (calls, meetings, notes, tasks) attached to Contacts or Opportunities map to Nutshell Tasks. Activity type is preserved as a custom Task field. Description, due date, and owner assignment transfer directly. Infor's interaction logs (Prospect Interactions, Customer Interactions) map to Tasks with a type of 'Log' and the interaction text in the description. Activity dates are preserved to maintain the timeline sequence in Nutshell's activity feed.

Infor's Sales Forecasts organized into Sales Periods (named date-range constructs) have no native Nutshell equivalent. We decompose each Sales Period into start_date and end_date and map forecast totals to a custom Deal field called Sales_Period_Total__c. The Sales Period name maps to a custom Deal field called Forecast_Period__c. The customer's admin rebuilds forecast groupings within Nutshell's pipeline and reporting views using these custom fields. This is documented explicitly in the field mapping spreadsheet.

Infor CRM Campaigns map to Nutshell Campaigns. Campaign type, status, start/end dates, and budget transfer to the corresponding Nutshell Campaign fields. Campaign Items linking products or contacts to a campaign are stored as a custom note in Nutshell's campaign record. Multi-contact campaign membership is not a first-class Nutshell object; we store it as a list of Person IDs in a custom field for admin reference.

Infor CRM's ticketing module stores cases with status, priority, assigned agent, and conversation history. Nutshell has no native ticket or case object. We migrate open Tickets as Notes attached to the related Company or Person record, with the Note title set to the Ticket subject and the body containing status, priority, assigned agent, and conversation history in a structured text format. Closed Tickets are not migrated by default; the customer can opt to include them as archived Notes. This limitation is disclosed during scoping.

Infor CRM Products and Price Lists map to Nutshell Products. Product name, SKU (product code), unit price, and description transfer directly. Infor's multi-tier pricing structures (Price List form with tiered pricing per quantity range) are complex to model in Nutshell; we map the base price and note tier complexity as a custom Product field for the customer to configure manually post-migration if the Nutshell plan supports custom fields on Products.

Infor CRM custom fields on Accounts, Contacts, Opportunities, and Tickets (user-defined picklists, dates, and lookups) are inventoried during discovery. Nutshell's custom field count is gated by plan tier. We map each Infor custom field to the nearest Nutshell equivalent (text, number, date, or picklist). Any Infor lookup field that references another Infor record type is mapped as a text field in Nutshell since Nutshell does not support cross-object lookup relationships on custom fields. The customer reviews and approves the custom field mapping before migration begins.