CRM migration
Field-level mapping, validation, and rollback between Infor CloudSuite Customer Relationship Management (CRM) and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Infor CloudSuite Customer Relationship Management (CRM)
Source
Freshsales
Destination
Compatibility
11 of 14
objects map 1:1 between Infor CloudSuite Customer Relationship Management (CRM) and Freshsales.
Complexity
BStandard
Timeline
4-8 weeks
Overview
Infor CloudSuite CRM and Freshsales serve different operational models. Infor CRM is sold as part of a CloudSuite Industrial or Distribution edition under an enterprise subscription negotiated with Infor sales, and it requires the Trans license module to function. Freshsales (Freshworks' CRM) is a per-seat SaaS product starting at $9 per user per month with a modern web interface and built-in Freddy AI assistant. The structural difference that drives migration complexity is Infor's tightly coupled relational schema: Accounts link to Contacts, Opportunities link to Accounts and Sales Periods, and Tickets carry multi-line conversation history. Freshsales uses a flat object model with Organizations, Contacts, Deals, and separate Activity objects. We resolve the hierarchy at migration time by loading Organizations first, then Contacts with Organization lookups, then Deals with Organization and Owner lookups, then Activities with their parent references. Sales Periods — Infor's named date-range forecast constructs — decompose into date boundaries applied to Deal close dates or stored as custom date-range fields in Freshsales. We do not migrate Infor BPM workflows, CRM Workflows, or Infor ION integrations; we deliver a written inventory of these for the customer's admin to rebuild in Freshsales.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Infor CloudSuite Customer Relationship Management (CRM) object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Infor CloudSuite Customer Relationship Management (CRM)
Account (Customer)
Freshsales
Organization
1:1Infor CRM Accounts (known as Customers form with CRM tab) store company-level data including SIC code, revenue, employee count, and territory assignments. These map directly to Freshsales Organizations. The Organization ID is the primary lookup key used to resolve Contact and Deal parent references during migration. Territory assignments from Infor CRM map to a custom Organization field because Freshsales does not have a native territory object at Growth tier.
Infor CloudSuite Customer Relationship Management (CRM)
Sales Contact
Freshsales
Contact
1:1Infor CRM Sales Contacts are linked to Accounts and store the individual contact's name, role, phone, and email. We map to Freshsales Contact with the Organization lookup resolved from the parent Account. Infor's Outlook export behavior (which creates duplicates rather than syncing) means we deduplicate on email address and name matching before landing contacts in Freshsales to avoid duplicate Contact records.
Infor CloudSuite Customer Relationship Management (CRM)
Opportunity
Freshsales
Deal
1:1Infor CRM Opportunities track deal stage, value, probability, and close date and link to Accounts. They map to Freshsales Deals with the Organization lookup resolved to the destination Account. Stage values transform to Freshsales Deal stages; Infor's probability field maps to a custom Deal field because Freshsales Deal stages do not carry native probability by default.
Infor CloudSuite Customer Relationship Management (CRM)
Lead (Prospect)
Freshsales
Lead
1:1Infor CRM Prospects and Leads are captured via the Prospects form and Leads form with conversion to Customer and Opportunity. We migrate the Lead record including status, source, and owner to Freshsales Lead. Lead status values map to Freshsales Lead status picklist. If the customer has both converted and unconverted Prospects in Infor, we separate them: converted Prospects map to Organizations (if company-level) or Contacts (if individual), and unconverted Prospects map to Freshsales Leads.
Infor CloudSuite Customer Relationship Management (CRM)
Sales Forecast
Freshsales
Deal (with custom date-range fields)
lossySales Forecasts in Infor CRM aggregate Opportunities into Sales Periods — named date ranges that define the fiscal or forecast period structure. Freshsales uses standard close date fields on Deals without a native Sales Period construct. We decompose the Sales Period into start and end date boundaries and apply them as custom date fields on the Deal record. Forecast totals aggregate via Freshsales custom reporting or a post-migration reporting rebuild.
Infor CloudSuite Customer Relationship Management (CRM)
Activity (Call, Meeting, Note, Task)
Freshsales
Calls, Meetings, Tasks, Notes
1:1Infor CRM Activities and Events track calls, meetings, notes, and tasks with due dates and owner assignments, stored against Contacts or Opportunities. We map each activity type to its Freshsales equivalent: Infor calls map to Freshsales Calls, meetings to Meetings, tasks to Tasks, and interactions with notes to Notes. Owner assignment resolves via User mapping by email. Activity timestamps preserve the original Infor date for timeline ordering.
Infor CloudSuite Customer Relationship Management (CRM)
Campaign and Campaign Item
Freshsales
Target List
1:manyInfor CRM Campaigns store campaign type, status, start/end dates, and budget, with Campaign Items linking products or contacts to a campaign. Freshsales does not have a native campaign object but has Target Lists for segmentation. We split the Infor campaign structure: campaign metadata (name, type, status, dates, budget) maps to a Freshsales custom object or a Target List with custom fields, and campaign members (Contacts) map to Target List members with the original campaign association preserved.
Infor CloudSuite Customer Relationship Management (CRM)
Ticket (Customer Service)
Freshsales
Case
1:1Infor CRM Tickets store support cases with status, priority, assigned agent, and multi-line conversation history, linked to Accounts and Contacts. We map to Freshsales Case with Organization and Contact lookups resolved from the parent Account and Contact. Multi-line ticket conversation history migrates as Case timeline entries (notes or tasks) attached to the Case. Ticket status and priority values map to Freshsales Case status and priority picklists.
Infor CloudSuite Customer Relationship Management (CRM)
Product and Price List
Freshsales
Product
1:1Infor CRM Products and price lists are managed for quoting within the CRM. The Price List form stores pricing tiers. We migrate the product catalog (product name, code, description) to Freshsales Product. Complex tiered pricing in Infor price lists requires validation: we assess whether the pricing tiers map to Freshsales Product price book entries or require a custom pricing field on the Deal line item.
Infor CloudSuite Customer Relationship Management (CRM)
Quote
Freshsales
Deal (with Products)
1:1Infor CRM Quotes are linked to Opportunities and Accounts and hold products, prices, and discounts. Freshsales does not have a separate Quote object at Growth and Pro tiers. We migrate Quote headers and line items as Deal-level custom fields or as Products attached to the Deal. Quote status (Draft, Sent, Accepted, Lost) maps to Deal stage or a custom Deal status field.
Infor CloudSuite Customer Relationship Management (CRM)
User (Owner)
Freshsales
User
1:1Infor CRM Users serve as record Owners and are linked to Territories. We map Infor Users to Freshsales Users by email match. Any Infor User without a matching Freshsales User goes to a reconciliation queue for the customer's admin to provision before record import resumes. Territory assignments from Infor are preserved as a custom field on the Freshsales User record if the customer requires territory-based reporting.
Infor CloudSuite Customer Relationship Management (CRM)
Custom Field (Accounts, Contacts, Opportunities, Tickets)
Freshsales
Custom Field
1:1Infor CRM supports custom fields with Infor-specific types (picklists, dates, lookups) on Accounts, Contacts, Opportunities, and Tickets. We inventory all custom fields during scoping, map each to the equivalent Freshsales custom field type (text, number, date, picklist, multi-select picklist), and provision them in Freshsales before data import. Infor picklist values map to Freshsales picklist options; Infor lookup fields require a separate mapping table if the lookup target is also migrating.
Infor CloudSuite Customer Relationship Management (CRM)
Attachment
Freshsales
Attachment
1:1Infor CRM Attachments can be stored against Contacts, Accounts, Opportunities, and Tickets. We export attachments to a file store and create links in Freshsales using the standard attachment object. Email attachments from Infor's Outlook integration also migrate via the file store path. Large binary attachments (over 10 MB) are flagged for separate handling because Freshsales attachment limits apply.
Infor CloudSuite Customer Relationship Management (CRM)
Group (Saved Query)
Freshsales
Smartlist or Tag
lossyInfor CRM Groups segment records using saved query definitions with a name. Freshsales has Smartlist filters and Tags but not a direct equivalent saved-query construct. We assess whether the Infor Group definitions map to Freshsales Smartlist criteria or require Tags as a simpler segmentation alternative. If the customer relies heavily on Infor Groups for segmentation, we recommend rebuilding them as Freshsales Smartlists post-migration.
| Infor CloudSuite Customer Relationship Management (CRM) | Freshsales | Compatibility | |
|---|---|---|---|
| Account (Customer) | Organization1:1 | Fully supported | |
| Sales Contact | Contact1:1 | Fully supported | |
| Opportunity | Deal1:1 | Fully supported | |
| Lead (Prospect) | Lead1:1 | Fully supported | |
| Sales Forecast | Deal (with custom date-range fields)lossy | Fully supported | |
| Activity (Call, Meeting, Note, Task) | Calls, Meetings, Tasks, Notes1:1 | Fully supported | |
| Campaign and Campaign Item | Target List1:many | Fully supported | |
| Ticket (Customer Service) | Case1:1 | Fully supported | |
| Product and Price List | Product1:1 | Fully supported | |
| Quote | Deal (with Products)1:1 | Fully supported | |
| User (Owner) | User1:1 | Fully supported | |
| Custom Field (Accounts, Contacts, Opportunities, Tickets) | Custom Field1:1 | Fully supported | |
| Attachment | Attachment1:1 | Fully supported | |
| Group (Saved Query) | Smartlist or Taglossy | Fully supported |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Infor CloudSuite Customer Relationship Management (CRM) gotchas
Outlook export creates duplicate contacts, not synced records
Usage-based API licensing gates customer-built integrations
Slow performance with large groups blocks export and migration prep
Sales Periods and forecast schema require explicit mapping
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Discovery and extraction assessment
We audit the Infor CRM instance across record counts (Accounts, Contacts, Opportunities, Leads, Activities, Tickets, Campaigns), custom field inventory, active Workflows, ION integrations, and Sales Period definitions. We assess the export path: if the API license allows sufficient throughput, we use Infor's REST API; otherwise, we use the group-based export in chunks. We identify Outlook integration duplicates, large group exports that require batched extraction, and any Infor-specific field types (lookups, picklists) requiring transform logic. The discovery output is a written migration scope document and an extraction plan specifying the primary and fallback paths for each object.
Schema design and Freshsales provisioning
We design the destination schema in Freshsales. This includes provisioning custom fields (matching Infor field types to Freshsales equivalents), setting up Deal stages mapped from Infor Opportunity stages, configuring picklist values, and creating any custom objects or fields required for Sales Period decomposition. If the customer requires territory management, we add custom fields for territory assignment on Users and Organizations. Schema is validated in a Freshsales sandbox or trial environment before any production data moves.
Deduplication and data cleansing
We run deduplication on Infor CRM contacts using email address as the primary key and name matching as secondary. Any records identified as Outlook-export duplicates are consolidated before migration. We apply data quality checks: standardizing phone number formats, resolving incomplete address records, and flagging records with missing required Freshsales fields. Dirty data that cannot be automatically resolved is documented in a cleansing queue for the customer's admin to address before migration or accepted with a known-data-quality caveat in the migration sign-off.
Sandbox migration and reconciliation
We run a full migration into a Freshsales sandbox environment using production-like data volume. The customer's operations lead reconciles record counts (Organizations in, Contacts in, Deals in, Activities in), spot-checks 25-50 random records against the Infor CRM source, and validates the Sales Period decomposition if applicable. Any mapping corrections are documented and the sandbox run is repeated or signed off before production migration begins.
Owner reconciliation and User provisioning
We extract every distinct Infor CRM User referenced as an Owner on any migrating record and match by email against the Freshsales destination User table. Any Infor User without a matching Freshsales User goes to a reconciliation queue. The customer's admin provisions missing Freshsales Users before production migration resumes. Territory assignments from Infor are mapped to custom User fields during this step if the customer has an active territory model.
Production migration in dependency order
We run production migration in record-dependency order: Organizations first (from Infor Accounts), then Contacts with Organization lookups resolved, then Deals with Organization and Owner lookups resolved, then Leads (unconverted Prospects), then Activities (Calls, Meetings, Tasks, Notes) with parent record lookups resolved, then Tickets as Cases with Organization and Contact lookups resolved, then Products, then Custom Fields. Each phase emits a row-count reconciliation report before the next phase begins. The Sales Period decomposition runs as a transform step applied to the Deal records during the Deals phase.
Cutover, final validation, and automation handoff
We freeze Infor CRM writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver the Workflow and ION integration inventory document to the customer's admin team for rebuild in Freshsales Workflows. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's team. We do not rebuild Infor CRM Workflows as Freshsales Workflows inside the migration scope; that is a separate engagement or an internal admin task.
Platform deep dives
Infor CloudSuite Customer Relationship Management (CRM)
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Infor CloudSuite Customer Relationship Management (CRM) and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Infor CloudSuite Customer Relationship Management (CRM): Not publicly documented — customer-built services are metered by usage minutes, requests, and storage under the license agreement.
Data volume sensitivity
Infor CloudSuite Customer Relationship Management (CRM) doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Infor CloudSuite Customer Relationship Management (CRM) to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Infor CloudSuite Customer Relationship Management (CRM) to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Infor CloudSuite Customer Relationship Management (CRM)
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.