ERP migration
Field-level mapping, validation, and rollback between Selly Erp and Infor CloudSuite Corporate. We move data and schema; workflows are rebuilt natively in Infor CloudSuite Corporate.
Selly Erp
Source
Infor CloudSuite Corporate
Destination
Compatibility
7 of 10
objects map 1:1 between Selly Erp and Infor CloudSuite Corporate.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Selly ERP to Infor CloudSuite is a migration from an SMB CRM with light ERP capabilities to a full enterprise cloud ERP built on AWS. Selly ERP stores contacts, deals, invoices, and activity history in a flat CRM-centric model without a documented API, meaning every record set must be extracted as a manual CSV dump from the in-app export function. Infor CloudSuite accepts external data through its Migration Utility, which connects to a source SQL database or accepts staged flat files with a defined import sequence. The key migration challenge is satisfying Infor's prerequisite sequencing: Business Partner and Item master records must exist before Sales Orders or Invoices can be imported. We extract Selly ERP's Customers, Leads, Deals, Quotes, Invoices, and Activities from the customer-provided CSV dumps, transform field names and value formats, and load them through Infor's Migration Utility or direct API in dependency order. Workflow automations and custom automation rules inside Selly ERP cannot be extracted and are delivered as a written specification for the customer's Infor administrator to rebuild post-migration.
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.
Source platform
Selly Erp platform overview
Scorecard, SWOT, gotchas, and pricing for Selly Erp.
Destination platform
Infor CloudSuite Corporate platform overview
Scorecard, SWOT, gotchas, and pricing for Infor CloudSuite Corporate.
Data migration guide
The complete Infor CloudSuite migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Destination checklist
Infor CloudSuite migration checklist
Pre- and post-cutover tasks for moving onto Infor CloudSuite Corporate.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Selly Erp object lands in Infor CloudSuite Corporate, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Selly Erp
Lead
Infor CloudSuite Corporate
Contact / Person Business Partner
1:1Selly ERP Leads map to Infor CloudSuite Business Partner records of type Person. We extract lead name, email, phone, source, and status from the CSV dump and map source to a custom Business Partner attribute field. Infor requires Business Partner to exist before any Sales Order can reference that party, so Leads are loaded in the first master-data phase. Status mapping is confirmed with the customer: open leads become Active, converted leads receive the conversion date as an attribute.
Selly Erp
Customer
Infor CloudSuite Corporate
Business Partner (Organization)
1:1Selly ERP Customer records map to Infor CloudSuite Business Partner of type Organization, with company details becoming address, billing address, and payment terms fields. We extract the billing address and any VAT or tax registration number from the customer dump. For B2C customers without a formal company name, we fall back to Person Business Partner with the individual as the primary contact. The Business Partner number in Infor becomes the primary account identifier for downstream transactional records.
Selly Erp
Deal
Infor CloudSuite Corporate
Sales Order
1:1Selly ERP Deals map to Infor CloudSuite Sales Orders. The deal name becomes the order description, deal value maps to the order total, and pipeline stage maps to an Infor order status or workflow stage. We extract the owner (sales rep) from the deal and resolve it to an Infor User during User provisioning. Deals without a linked Customer require the customer record to be loaded first; we flag these as orphaned and resolve before the order import phase.
Selly Erp
Quote
Infor CloudSuite Corporate
Sales Quote
1:1Selly ERP Quotes map to Infor CloudSuite Sales Quotes. Quote line items require Product2 records to exist in Infor, so we verify or pre-load the product catalog before Quotes are imported. Quote validity dates and totals migrate as structured fields; custom quote templates and branding do not transfer and must be reproduced in Infor's template designer post-migration.
Selly Erp
Invoice
Infor CloudSuite Corporate
Invoice / Accounts Receivable Invoice
1:1Selly ERP Invoices map to Infor CloudSuite Accounts Receivable Invoice records. Invoice header data (number, date, customer, total) migrates as structured records. We archive the original PDF separately and attach it to the corresponding invoice record in Infor IDM (Infor Document Management) as a reference copy. Invoice line items are migrated as invoice distribution lines where the destination schema supports line-level detail; any line items that cannot be mapped are flagged for manual re-entry or a supplemental import.
Selly Erp
Activity (Call, Email, Meeting, Note, Task)
Infor CloudSuite Corporate
Activity / Interaction Log
1:manySelly ERP activity records (calls, emails, meetings, tasks, notes) attached to contacts or deals are consolidated and mapped to Infor CloudSuite Activity records. Infor uses a unified activity model with sub-types for calls, appointments, and tasks. We preserve the original timestamp, subject, body content, and owner assignment. Attachments linked to activities in Selly ERP are extracted and re-uploaded to Infor Document Management (IDM) linked to the corresponding activity record.
Selly Erp
Pipeline Stage
Infor CloudSuite Corporate
Sales Order Status / Workflow Stage
lossySelly ERP custom pipeline stage names are extracted during scoping and mapped to Infor CloudSuite order status values or workflow stage codes. We confirm the full stage list with the customer and configure corresponding status codes in Infor before any transactional records are imported. Stage probabilities from Selly ERP are stored as custom attributes on the order status configuration in Infor.
Selly Erp
User / Owner
Infor CloudSuite Corporate
User
1:1Selly ERP user accounts map to Infor CloudSuite Users. We extract every distinct owner referenced on Leads, Customers, Deals, Quotes, Invoices, and Activities and match by email address against the destination Infor tenant's user list. Any owner without a matching Infor User is placed in a reconciliation queue for the customer's admin to provision before record import resumes. Archived or inactive Selly ERP users are flagged for inactivation in Infor.
Selly Erp
Custom Field
Infor CloudSuite Corporate
Custom Field
lossyCustom fields on any Selly ERP object (Lead, Customer, Deal, Quote, Invoice) are extracted from the export dump and preserved as custom fields in Infor CloudSuite. We create matching fields in Infor using Infor's field administration tools before importing values. Field data types are mapped: text to string, number to decimal or integer, date to date, and checkbox to boolean. The customer confirms the intended Infor field placement (on the Business Partner form, Order form, or as an extended attribute) during scoping.
Selly Erp
Attachment
Infor CloudSuite Corporate
Infor Document Management (IDM)
1:1File attachments linked to records in Selly ERP are extracted from the export and stored separately for re-upload to Infor Document Management (IDM). We map each file to the corresponding Business Partner, Sales Order, or Invoice record in Infor using a naming convention that preserves the original record context. Infor IDM is the standard container for migrated documents; we do not attach files directly to transactional records as inline blobs.
| Selly Erp | Infor CloudSuite Corporate | Compatibility | |
|---|---|---|---|
| Lead | Contact / Person Business Partner1:1 | Fully supported | |
| Customer | Business Partner (Organization)1:1 | Fully supported | |
| Deal | Sales Order1:1 | Fully supported | |
| Quote | Sales Quote1:1 | Fully supported | |
| Invoice | Invoice / Accounts Receivable Invoice1:1 | Fully supported | |
| Activity (Call, Email, Meeting, Note, Task) | Activity / Interaction Log1:many | Fully supported | |
| Pipeline Stage | Sales Order Status / Workflow Stagelossy | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| Attachment | Infor Document Management (IDM)1:1 | 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.
Selly Erp gotchas
No public API forces manual data export
Invoice PDFs are not exported as structured records
Workflow automations are undocumented and non-transferable
Infor CloudSuite Corporate gotchas
Infor OS tier-based usage limits gate API and BaaS capabilities
Custom Fields use inconsistent naming across Infor editions
SQL migration utility requires source database access
Multi-site and multi-currency data require separate period closure sequencing
REST API payload and timeout limits restrict bulk migration throughput
Pair-specific challenges
Migration approach
Discovery and export preparation
We audit the Selly ERP account across all active modules (Leads, Customers, Deals, Quotes, Invoices, Activities, Custom Fields) and identify every distinct export that must be produced manually by the customer. We provide a step-by-step export guide tailored to the Selly ERP UI, with specific instructions per module including filter settings, date ranges, and field selection. We also extract the pipeline stage list, owner list, and any custom field definitions from the customer's account during the discovery call. The discovery output is a written migration scope and an export checklist for the customer to complete before the first ingestion session.
Infor target schema design and master data configuration
We design the destination Infor CloudSuite schema based on the exported Selly ERP data and the customer's Infor edition. This includes configuring Business Partner types (Person and Organization), address structures, payment terms, tax codes, and currency settings. We pre-create any custom fields identified in the Selly ERP export. We map Selly ERP pipeline stages to Infor order status codes and configure the corresponding workflow stages. Schema is designed in a staging environment or documented for the customer's Infor administrator to deploy before production migration begins.
Export validation and data profiling
The customer delivers the CSV dumps from Selly ERP. We run a data profiling pass on each file: record counts, field-level completeness, date format validation, duplicate detection, and orphaned record identification (e.g., Deals referencing Customers that are missing from the export). We produce a data quality report for each module and work with the customer to resolve gaps. Common issues include missing Customer IDs on Deals, blank owner fields, and date fields in mixed formats. No data is loaded into Infor until the profiling report is signed off.
Master data migration in dependency order
We load master data into Infor CloudSuite before any transactional records. The sequence is: Business Partners (Person first, then Organization), Items and Product master, Tax Codes, Payment Terms, and Currency configurations. Each phase emits a row-count reconciliation report against the source export before the next phase begins. Any Business Partner or Item records missing from the export are flagged for manual entry in Infor before transactional import resumes. This phase uses Infor's Migration Utility or direct API depending on the destination edition and available endpoints.
Transactional record migration
With master data in place, we load transactional records in dependency order: Quotes, then Sales Orders (from Deals), then Invoice records. Each phase is preceded by a mapping walkthrough with the customer to confirm that Selly ERP field values map correctly to Infor fields (e.g., deal stage to order status, quote validity to Infor quote expiry). We archive invoice PDFs to Infor Document Management during this phase. Activity records (calls, emails, meetings, tasks, notes) are loaded last using Infor's activity API, with timestamps normalised to the destination timezone and owner assignments resolved to Infor Users.
Cutover, validation, and automation rebuild handoff
We freeze Selly ERP writes during the cutover window and run a final delta migration of any records created or modified during the migration period. We perform a reconciliation pass comparing record counts in Infor against the original source export, with spot-checks on 25-50 records per module. We deliver the Automation and Workflow Specification document to the customer's Infor administrator, covering every active Selly ERP rule with its trigger, conditions, actions, and recommended Infor OS equivalent. We do not rebuild Selly ERP automations as Infor workflows inside the migration scope; that is a separate engagement.
Platform deep dives
Selly Erp
Source
Strengths
Weaknesses
Infor CloudSuite Corporate
Destination
Strengths
Weaknesses
Complexity grading
Standard ERP migration. 1 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 Selly Erp and Infor CloudSuite Corporate.
Object compatibility
1 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
Selly Erp: Not publicly documented.
Data volume sensitivity
Selly Erp 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 Selly Erp to Infor CloudSuite Corporate migration scoping. Not seeing yours? Book a call.
Walk through your Selly Erp to Infor CloudSuite Corporate migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Selly Erp
Other ways to arrive at Infor CloudSuite Corporate
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.