Marquis IQ holds certified connectors for Infor CloudSuite Industrial, SyteLine, LX (BPCS), M3 (MAPICS), and VISUAL ERP, the broadest Infor coverage in manufacturing analytics. Whichever version your sites run, Marquis connects it.
Infor has grown largely through acquisition. CloudSuite Industrial (formerly SyteLine, now cloud-hosted), SyteLine v8 (on-premises), LX (formerly BPCS, running on IBM i), M3 (formerly MAPICS), and VISUAL ERP are all "Infor products", but they share almost nothing at the database level. Different schemas, different connection methods, different reporting tools. Each one requires a different approach to extract data reliably.
For PE firms that have acquired companies over time, an Infor portfolio can mean three or four fundamentally different systems that happen to share a vendor name. Getting a single P&L view across them requires a connector strategy that actually accounts for each platform's architecture, not a one-size-fits-all approach that works for one and breaks for the others.
Each Infor product has its own connection architecture, schema conventions, and data model. Marquis maintains a dedicated connector for each, not a generic adapter that pretends they're the same system.
The cloud-hosted successor to SyteLine, CloudSuite Industrial runs on Infor OS and uses the ION API as its integration layer. Marquis connects via ION. Infor's own middleware, to extract production, financial, and supply chain data without direct database access. CSI's cloud release cadence is handled by the ION API contract, not by manual schema updates.
The on-premises version of SyteLine, still running at thousands of manufacturing sites. SyteLine v8 uses SQL Server as its database backend, and Marquis connects via ODBC with deep schema knowledge of SyteLine's table structure, how production orders, work centers, costing, and multi-site configurations are stored in the SyteLine data model.
Infor LX, formerly BPCS, runs on IBM i (AS/400) infrastructure, which is a fundamentally different extraction environment than a Windows-based SQL Server ERP. Marquis connects via ODBC over the IBM i data extraction layer, with schema knowledge specific to LX's file structure, including how BPCS organizes its manufacturing and distribution data across its AS/400 physical files.
Infor M3, formerly MAPICS, is Infor's solution for process and mixed-mode manufacturers. M3 is available in both cloud-hosted and on-premises configurations. Marquis connects to cloud M3 via the H5 API. Infor's published web services interface for M3, and to on-premises M3 via ODBC. The connector handles both deployment modes with the same output schema, so mixed M3 deployments are supported within a single portfolio.
Infor VISUAL is a job-shop-oriented ERP built for discrete manufacturers running engineer-to-order and make-to-order operations. VISUAL stores its data in SQL Server and Marquis connects via ODBC, with specific schema knowledge of how VISUAL structures its job costing, work order management, and shop floor tracking data. VISUAL's manufacturing-centric data model requires a different extraction approach than general-ledger-first ERPs.
The temptation with Infor is to treat it as one product. CSI, SyteLine, LX, M3, and VISUAL have almost nothing in common at the database level. Each connector Marquis built is specific to the platform it connects.
We had three sites. CloudSuite at the platform, SyteLine v8 at an acquisition, and LX at another. Every other vendor we talked to said they could connect "Infor." Marquis was the only one who knew that CSI, SyteLine, and LX are basically three different ERPs that happen to share a logo.
CloudSuite Industrial, SyteLine v8, LX (BPCS), M3 (MAPICS), VISUAL, or some combination across sites. We'll tell you which connector applies to each and walk through what analytics are live from day one.
We'll confirm which Infor connector applies to your specific version and deployment model before we start.