ERP migration

Migrate from Selly Erp to Infor CloudSuite Corporate

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 logo

Selly Erp

Source

Infor CloudSuite Corporate

Destination

Infor CloudSuite Corporate logo

Compatibility

70%

7 of 10

objects map 1:1 between Selly Erp and Infor CloudSuite Corporate.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Selly Erp logo

Selly Erp

What's pushing teams away

  • Third-party ERP integrations are limited — existing accounting or inventory systems do not integrate smoothly with open platforms, forcing manual data re-entry.
  • Technical studios and businesses with specialist workflow needs report that Selly ERP requires significant customisation workarounds to fit their use case, which some find unsustainable.
  • Customers migrating away report that the platform lacks a well-documented public API, making automated data extraction difficult and dependent on in-app exports.
  • The analytics and reporting module is described as functional but not deep — power users needing custom dashboards or advanced forecasting outgrow the built-in capabilities.

Choosing

Infor CloudSuite Corporate logo

Infor CloudSuite Corporate

What's pulling them in

  • Infor CloudSuite is industry-specific out of the box — manufacturing, distribution, healthcare, and food & beverage editions ship with preconfigured workflows that reduce the need for extensive customization and accelerate time to value for operations-heavy organizations.
  • The platform's deep integration with Excel for financial reporting is frequently cited as a key productivity feature, allowing finance teams to pull data directly and make changes without leaving familiar tooling.
  • AWS-hosted multi-tenant deployment eliminates data center management for IT teams, and Infor OS provides a unified integration layer (ION) that connects the CloudSuite to third-party applications without point-to-point middleware.
  • Organizations with multi-site or multi-country operations choose Infor for its multicurrency, multilanguage, and local regulatory compliance capabilities across 175+ countries, which simplifies consolidation for global CFOs.
  • The two-tier ERP strategy positioning lets corporate headquarters run CloudSuite while subsidiaries run lighter instances, which appeals to complex organizational structures that want standardization without full replacement.

Object mapping

How Selly Erp objects map to Infor CloudSuite Corporate

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

maps to

Infor CloudSuite Corporate

Contact / Person Business Partner

1:1
Fully supported

Selly 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

maps to

Infor CloudSuite Corporate

Business Partner (Organization)

1:1
Fully supported

Selly 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

maps to

Infor CloudSuite Corporate

Sales Order

1:1
Fully supported

Selly 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

maps to

Infor CloudSuite Corporate

Sales Quote

1:1
Fully supported

Selly 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

maps to

Infor CloudSuite Corporate

Invoice / Accounts Receivable Invoice

1:1
Fully supported

Selly 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)

maps to

Infor CloudSuite Corporate

Activity / Interaction Log

1:many
Fully supported

Selly 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

maps to

Infor CloudSuite Corporate

Sales Order Status / Workflow Stage

lossy
Fully supported

Selly 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

maps to

Infor CloudSuite Corporate

User

1:1
Fully supported

Selly 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

maps to

Infor CloudSuite Corporate

Custom Field

lossy
Fully supported

Custom 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

maps to

Infor CloudSuite Corporate

Infor Document Management (IDM)

1:1
Fully supported

File 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.

Gotchas + challenges

What specifically takes care here

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 logo

Selly Erp gotchas

High

No public API forces manual data export

Medium

Invoice PDFs are not exported as structured records

Medium

Workflow automations are undocumented and non-transferable

Infor CloudSuite Corporate logo

Infor CloudSuite Corporate gotchas

High

Infor OS tier-based usage limits gate API and BaaS capabilities

Medium

Custom Fields use inconsistent naming across Infor editions

Medium

SQL migration utility requires source database access

Medium

Multi-site and multi-currency data require separate period closure sequencing

Low

REST API payload and timeout limits restrict bulk migration throughput

Pair-specific challenges

  • Selly ERP has no public API — manual CSV export is mandatory

    Selly ERP does not publish a REST, GraphQL, or Bulk API. We cannot initiate automated record retrieval. The customer must log into Selly ERP and use the in-app export function to produce CSV or Excel dumps of each module: Leads, Customers, Deals, Quotes, Invoices, Activities, and Custom Fields. This export must be performed manually per module, and the quality of the output depends on how the customer navigates the UI. We plan additional scoping time for the customer to prepare and validate the export files before ingestion begins. If the customer cannot produce a complete export of a particular module, that module is flagged as a partial or manual migration risk.

  • Infor requires master data before transactional records

    Infor CloudSuite enforces referential integrity that Selly ERP does not. Business Partner records must exist before Sales Orders can reference them. Item master records must exist before Quote or Invoice line items can reference a product. Tax codes, payment terms, and currency codes must be configured before they appear on any transactional form. We sequence the migration as master data first (Business Partners, Items, Tax Codes, Payment Terms), then transactional records (Quotes, Sales Orders, Invoices), then activities. Any records in the export that reference missing master data are held in a reconciliation queue until the prerequisite is loaded.

  • Invoice PDFs are not exported as structured records

    Selly ERP generates invoice PDFs linked to customer records, but these are not reliably available as structured data in the export. We archive the PDF files separately and link them to the corresponding Business Partner or Invoice record in Infor Document Management (IDM) as a reference copy. Invoice line items must be re-imported as structured records manually or through a supplemental line-item import. The original PDF serves as a reference only; it does not replace the structured invoice data in Infor.

  • Workflow automations cannot be extracted from Selly ERP

    Selly ERP workflow rules, triggers, and automated sequences configured inside the platform are not accessible as extractable data. We cannot migrate them to Infor CloudSuite directly. During discovery, we document every active automation from the customer's Selly ERP account and produce a written specification that maps each rule to its equivalent in Infor OS workflow or ION integration. The customer's Infor administrator rebuilds these post-migration. This is a manual step the customer must budget time for after go-live.

  • Report definitions and custom dashboards do not migrate

    Selly ERP report definitions, saved filters, and custom dashboard configurations are platform-specific and cannot be exported as reusable data. Infor CloudSuite provides Birst BI for analytics and embedded reporting, but report logic must be rebuilt from scratch. We deliver a written inventory of every Selly ERP report and saved view as a reference for the customer's Infor team to reproduce in Birst or Infor's standard reporting tools.

Migration approach

Six steps for a successful Selly Erp to Infor CloudSuite Corporate data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

Context on both ends of the pair

Selly Erp logo

Selly Erp

Source

Strengths

  • Flat per-user pricing without per-module add-ons keeps costs predictable for SMB teams
  • Covers the full sales cycle from lead capture through invoicing in one subscription
  • Italian-language customer support receives consistently high marks in user reviews
  • Google Workspace integration with Gmail and Google Drive out of the box
  • Suitable for small to mid-sized businesses that do not need enterprise-level customisation depth

Weaknesses

  • No publicly documented API — automated export is not possible without a manual in-app data dump
  • Limited third-party integrations; existing ERP and accounting tools do not connect smoothly
  • Reporting and analytics are functional but lack the depth power users require
  • Customisation for specialist industries requires workarounds rather than native configuration
  • Platform originated in Italy and documentation is primarily in Italian, limiting accessibility for international teams
Infor CloudSuite Corporate logo

Infor CloudSuite Corporate

Destination

Strengths

  • Industry-specific preconfiguration across manufacturing, distribution, healthcare, and food & beverage reduces post-implementation customization effort.
  • Deep Excel integration for financial reporting allows finance teams to export, manipulate, and push data back without leaving a familiar environment.
  • Multi-tenant AWS deployment with Infor OS provides a unified integration layer that simplifies connecting to third-party applications and legacy systems.
  • Strong multicurrency, multilanguage, and regulatory localization capabilities support organizations operating across 175+ countries from a single platform.
  • Modular architecture allows organizations to deploy core financials, supply chain, or manufacturing modules independently and expand over time.

Weaknesses

  • Opaque pricing model with no public per-user rates and deployments commonly ranging from $500K to $5M creates significant budget uncertainty for prospective buyers.
  • Implementation complexity and timeline (commonly 2+ years for large deployments) leads to extended periods of reduced productivity and elevated project risk.
  • Steep learning curve with hidden options and a lack of public setup guidance makes self-service onboarding difficult compared to competitors with richer documentation communities.
  • Manufacturing module functionality is perceived by some users as outdated relative to modern ERP platforms, with reported bug issues that require workarounds.
  • Tight coupling between modules and environment-specific configurations makes migration to non-Infor systems labor-intensive, increasing switching costs.

Complexity grading

How hard is this migration?

Standard ERP migration. 1 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Selly Erp and Infor CloudSuite Corporate.

  • Object compatibility

    B

    1 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Selly Erp: Not publicly documented.

  • Data volume sensitivity

    B

    Selly Erp doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Selly Erp to Infor CloudSuite Corporate migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Selly Erp to Infor CloudSuite Corporate data migrations

Answers to the questions buyers ask most during Selly Erp to Infor CloudSuite Corporate migration scoping. Not seeing yours? Book a call.

Can't find your answer?

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 consultation

Most migrations land between three and five weeks for accounts under 10,000 customer records, 3,000 deals, and no complex multi-site inventory. Migrations with large invoice histories (over 5,000 records), multi-currency data, extensive custom fields, or items requiring a pre-load product catalog move to eight to fourteen weeks because of master data sequencing, data profiling time, and Infor field creation scope. The Infor CloudSuite implementation itself typically runs nine to eighteen months end-to-end; FlitStack AI's migration scope covers the data migration portion within that timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Selly Erp.
Land in Infor CloudSuite Corporate, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day