Migrate your PILOT:Suite data
An ERP suite targeting manufacturing, distribution, and wholesale operations with integrated financials, inventory, and supply chain management.
In its favor
Why people choose PILOT:Suite
The signal that keeps PILOT:Suite on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
Process-industry focus since 1990 — workflows, terminology, and data models reflect chemical, pharmaceutical, and food-and-beverage manufacturing rather than discrete production patterns.
Combines production, quality, energy, and supply-chain management on one platform, removing the multi-vendor integration burden that comes from running separate MES, QMS, EMS, and SCM tools.
Web-based deployment with native iOS, Android, and iPad apps gives operators floor-level mobility without a dedicated handheld hardware stack.
Hierarchical organizational model with per-unit rights, roles, and multilingual support fits multi-site European manufacturers operating across language regions.
Available as a cloud variant for customers that want managed infrastructure rather than running MES on-premise, while still preserving the same data model.
No public reviews on Capterra (0 reviews recorded) make peer validation effectively impossible during evaluation.
Pricing is fully sales-led with no published tiers, making early-stage budget conversations difficult.
Mid-market and enterprise MES competitors (Rockwell PlantPAx, Siemens Opcenter, Aveva) have larger partner ecosystems and broader IIoT integration libraries.
Felten Group is a German-rooted vendor — partner coverage and support depth outside DACH and Europe may be thinner than buyers expect.
Custom integrations to ERP and CMMS systems require Felten Group services rather than a self-serve API marketplace.
Reasons to switch
Why people leave PILOT:Suite
The recurring reasons buyers give for replacing PILOT:Suite. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where PILOT:Suite fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
PILOT:Suite pricing overview
PILOT:Suite pricing is sales-led; Felten Group does not publish standard tiers. A free trial is available per Capterra, but per-user, per-site, and per-module pricing is quoted following a discovery call. Implementation, training, and integration to existing ERP/CMMS systems are quoted separately and are typically a significant portion of total first-year spend for MES rollouts of this complexity.
Custom (Sales-Led)
Tier 1 of 1
Custom — quoted per site and module
What's included
Need help selecting your ERP?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on PILOT:Suite's schedule — see our quote-based pricing →
What gets migrated
PILOT:Suite object support
Object-by-object support for PILOT:Suite migrations. Per-pair details surface during scoping.
Chart of Accounts
Not in this platformPILOT:Suite is an MES, not a financial ledger. Cost accounting data flows to the connected ERP rather than living in PILOT:Suite.
Customers
Mapping requiredCustomers appear as supply-chain participants (consignees on shipments, owners of customer-specific batches) rather than as a primary CRM object. We map customer codes during extract for downstream ERP alignment.
Vendors
Fully supportedSuppliers are first-class entities in the supply-chain module. We extract supplier master data with associated PO and quality records.
Items
Fully supportedItems (materials, intermediates, finished goods) carry full attribute sets including units of measure, quality specs, and batch/lot configuration. We preserve item master data with all linked specifications.
Transactions
Fully supportedProduction transactions (order start/stop, consumption, yield, scrap, quality events) are the heart of the MES data layer. We extract the transaction log per order with timestamps and operator attribution.
Inventory
Fully supportedInventory positions by warehouse and lot are tracked in real time. We snapshot inventory at cutover and migrate movement history for the agreed historical window.
Purchase Orders
Mapping requiredPOs appear in the supply-chain integration layer. Full PO history typically lives in the connected ERP; we extract whatever PO references PILOT:Suite holds for traceability continuity.
Budget
Not in this platformBudget data is not part of the MES data model. Budget vs actual reporting is built in the connected ERP or BI layer using PILOT:Suite production data as one input.
| Object | Support | Notes |
|---|---|---|
| Chart of Accounts | Not in this platform | PILOT:Suite is an MES, not a financial ledger. Cost accounting data flows to the connected ERP rather than living in PILOT:Suite. |
| Customers | Mapping required | Customers appear as supply-chain participants (consignees on shipments, owners of customer-specific batches) rather than as a primary CRM object. We map customer codes during extract for downstream ERP alignment. |
| Vendors | Fully supported | Suppliers are first-class entities in the supply-chain module. We extract supplier master data with associated PO and quality records. |
| Items | Fully supported | Items (materials, intermediates, finished goods) carry full attribute sets including units of measure, quality specs, and batch/lot configuration. We preserve item master data with all linked specifications. |
| Transactions | Fully supported | Production transactions (order start/stop, consumption, yield, scrap, quality events) are the heart of the MES data layer. We extract the transaction log per order with timestamps and operator attribution. |
| Inventory | Fully supported | Inventory positions by warehouse and lot are tracked in real time. We snapshot inventory at cutover and migrate movement history for the agreed historical window. |
| Purchase Orders | Mapping required | POs appear in the supply-chain integration layer. Full PO history typically lives in the connected ERP; we extract whatever PO references PILOT:Suite holds for traceability continuity. |
| Budget | Not in this platform | Budget data is not part of the MES data model. Budget vs actual reporting is built in the connected ERP or BI layer using PILOT:Suite production data as one input. |
Gotchas
What to watch for in PILOT:Suite migrations
Issues we've hit on past PILOT:Suite migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
Vendor-implemented system with no public developer portal
Process-industry data model differs from discrete-manufacturing MES
No published reviews complicate gotcha discovery
Mobile apps and web UI run against the same relational database
| Severity | Issue |
|---|---|
| High | Vendor-implemented system with no public developer portal |
| Medium | Process-industry data model differs from discrete-manufacturing MES |
| Medium | No published reviews complicate gotcha discovery |
| Low | Mobile apps and web UI run against the same relational database |
Leaving PILOT:Suite?
Where PILOT:Suite customers move next
6 destinations PILOT:Suite can migrate to.
How a PILOT:Suite migration works
Four steps, PILOT:Suite-specific
Connect
Not publicly documented. Felten Group's published material references 'set up connections to third-party platforms' but does not expose a public developer portal or API reference. Auth flow is established during the Felten Group integration engagement. into PILOT:Suite. Scopes limited to read-only on the data we move.
Map
We translate PILOT:Suite-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate PILOT:Suite quirks before production.
Migrate
Full migration with PILOT:Suite rate-limit handling. Rollback available throughout.
FAQ
PILOT:Suite migration FAQ
Answers to the questions buyers ask most during PILOT:Suite migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your PILOT:Suite migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate PILOT:Suite.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your PILOT:Suite setup and destination — written quote back within a business day.