SAP MII Migration for Small and Mid-Size Manufacturers

By Riley Quinn on May 15, 2026

sap-mii-migration-small-mid-size-manufacturers

Every SAP MII migration guide on the internet is written for enterprises with 8-figure IT budgets, 6-person internal project teams, and 18-month timelines. Small and mid-size manufacturers run on different math — 1-3 person IT teams, $80K-$300K total budget, and a CFO who needs to see the migration paid back inside the program. SAP MII mainstream support ends December 2027, and the cloud-only SAP DM path was not designed for SME-scale operations. The right answer for the 200-line knit factory, the 80-machine job shop, the 12-vessel specialty chemical plant is a right-sized lift-and-shift onto on-prem AI hardware — pilot to live in 8-12 weeks, perpetual license, source code included. Book a 30-minute SME migration walkthrough with our deployment engineers.

RIGHT-SIZED · 8-12 WEEKS · PERPETUAL LICENSE
SAP MII Migration Designed for SME Manufacturers. Not Enterprise Math Stretched Down.
SME manufacturers face migration constraints enterprise playbooks ignore — small IT teams, fixed budgets, single-site scope, no spare project manager, S/4HANA upgrade often happening in parallel. The right-sized path lifts the SAP MII workload onto on-prem AI hardware behind your firewall in 8 to 12 weeks. One-time cost. No subscription. The CFO sees the line item once. The plant team gets live use cases inside the program.
Powered by Right-Sized NVIDIA On-Prem Hardware
Jetson AGX Orin · Shop Floor Bridge
RTX PRO 5000 · MII Replacement Core
Optional DGX · skip on Tier 1
8-12 wk
SME fast-track · pilot to live
1-3
IT staff needed · part-time during cutover
$0/mo
Perpetual license · no SaaS subscription
Dec 2027
SAP MII mainstream support ends
SME MIGRATION · 8-WK PLAN v1.0 YOUR PLANT · SNAPSHOT 1 site · 1 MII server · 38 transactions 12 integrations · 2 IT staff · $180K budget WEEK-BY-WEEK ROADMAP W1-2 Discovery · scope freeze W3-4 Hardware install · OPC mapping W5-6 First use case live W7-8 Cutover ▮ ONE-TIME COST $180K License + HW + impl ▮ SAP DM 5-YR $640K License + impl + SaaS ▮ PAYBACK TIMELINE Break-even in month 11 $460K cumulative savings over 5 years

The SME Reality Check · Where Enterprise Migration Playbooks Break Down

Most SAP MII migration content is written from the enterprise side of the room. Here is what changes when the same problem lands at a 1-site, 2-person IT, $200K-budget manufacturer.

01
BUDGET
ENTERPRISE
$800K-$3M total
SME REALITY
$80K-$300K ceiling
Cloud-only SaaS at $40K-$80K/year fails the CFO test. Perpetual license fits.
02
TIMELINE
ENTERPRISE
12-24 month rollout
SME REALITY
8-12 weeks · live use cases
SME plants cannot freeze IT for 18 months. Right-sized lift-and-shift compresses to 8-12 weeks.
03
TEAM SIZE
ENTERPRISE
5-8 person internal team
SME REALITY
1-3 IT · part-time
No dedicated project manager. Vendor must drive 80% of the migration work.
04
CUSTOMIZATION
ENTERPRISE
137+ transactions · heavy ABAP
SME REALITY
20-60 transactions · mostly standard
Light customization = faster lift-and-shift. SAP DM clean-core redesign is overkill.
05
DEPLOYMENT
ENTERPRISE
Multi-site rollout · 3+ plants
SME REALITY
1 site · 1 server · 1 control room
No need for multi-tenant cloud. On-prem tower under a desk fits the site.
06
RISK TOLERANCE
ENTERPRISE
Multi-quarter parallel run
SME REALITY
2-week parallel · then cut
SMEs cannot afford prolonged dual-system overhead. Faster cutover, smaller risk window.
RIGHT-SIZED MIGRATION · DESIGNED FOR SME CONSTRAINTS
8-12 weeks · $80-300K · 1-3 IT staff · perpetual license

The point is not that enterprise migrations are wrong — they fit the math of multi-site operators with $1M+ budgets and 6-person internal teams. The point is that SME plants are running different math and need a different deployment model. Book a 30-minute walkthrough where we map a right-sized plan against your actual MII estate.

What's Included in the Right-Sized SME Package · Line by Line

The line item your CFO sees on the purchase order. Four pillars covering hardware, platform, integration work, and post-cutover support — priced as a single one-time engagement, not as monthly subscription drip. Talk to our SME support team about your specific scope.

PILLAR 01
ON-PREM HARDWARE
  • Jetson AGX Orin shop-floor bridge box (1 unit)
  • RTX PRO 5000 tower for MII workload
  • Pre-imaged, pre-tested, plug-and-power
  • 3-year manufacturer warranty included
$32K-$48K · one-time
PILLAR 02
PLATFORM LICENSE
  • Perpetual license · buy once, own forever
  • Source code included · modify it freely
  • All modules · OEE, downtime, KPI, dashboards
  • Unlimited users at the site · no per-seat fees
$80K-$140K · one-time
PILLAR 03
INTEGRATION WORK
  • 4-week discovery · MII inventory · scope freeze
  • OPC-UA tag mapping · ported as configuration
  • S/4HANA or ECC connection · OData, RFC, IDoc
  • Operator training + change-management collateral
$55K-$85K · one-time
PILLAR 04
POST-CUTOVER SUPPORT
  • 12 months hyper-care · response in business hours
  • Quarterly platform updates · install assistance
  • One use-case extension included (year 1)
  • Optional AMC after year 1 · ~12% of license
$15K-$28K · year 1
SME TOTAL · ALL FOUR PILLARS
$182K - $301K
One-time engagement · no SaaS subscription · CFO sees the line once
SAP DM EQUIVALENT · 5-YEAR TCO
$640K - $1.1M
License + impl + 5 years of $52K-$90K annual SaaS

Two Real SME Scenarios · How the On-Prem Stack Solves Them

Two real scenarios from SME manufacturers who replaced SAP MII with the right-sized iFactory on-prem stack. Each shows the constraint the enterprise playbook ignored and the hardware integration that closed it. Book a 30-minute walkthrough where we run the right-sized plan against your scenario.

SCENARIO 01
"We are a 200-line knit factory with 2 IT staff and a $200K migration budget. SAP partner quoted $720K + 14 months for SAP DM. We do not have either. What is the right-sized path?"
THE PROBLEM
Knit fabric manufacturer in Tirupur. 200 circular knitting machines (Mayer & Cie and Karl Mayer mix). One SAP MII production server. 42 transactions covering machine connectivity, OEE dashboards, downtime tracking, and IDoc handoff to S/4HANA. SAP partner quoted $720K for SAP DM migration plus $52K annual SaaS subscription on top, 14-month timeline, 1 full-time PM expected from the customer side. The plant has 2 IT staff total and $200K budgeted. The math does not work.
HOW THE ON-PREM STACK SOLVES IT
The Shop Floor Bridge (Jetson)
Replaces the MII PLC connectivity layer. Connects to 200 knitting machines via OPC-UA. Tag mappings ported from MII as configuration in 5 days — no rewriting of business logic.
The Right-Sized Core (RTX PRO 5000)
Runs OEE, downtime tracking, and S/4HANA IDoc handoff — the entire 42-transaction workload — on a single tower computer that fits under the IT lead's desk. SaaS subscription not needed.
8-Week Cutover
Pilot live in week 6 on 20 machines, full cutover in week 8. Vendor team handles 80% of the work. Plant's 2 IT staff stay on their day jobs and review weekly.
THE RESULT
Live in 8 weeks at $185K all-in. $535K saved vs SAP DM path. CFO approved on the first review.
SCENARIO 02
"We are a 12-vessel specialty chemical plant. MII handles batch records and OEM customer audit trail. SAP DM cloud-only fails our customer contracts that require on-prem data. What now?"
THE PROBLEM
Specialty chemical contract manufacturer. 12 reactor vessels producing fine chemicals for two top-20 pharma OEMs. SAP MII handles batch genealogy, reactor parameter capture, deviation logging, and audit-trail export. Both OEM contracts contain explicit on-prem data residency clauses — production-floor data cannot live in a hyperscaler tenant. SAP DM is cloud-only. Migration risks contract violations worth $18M annual revenue. SME budget rules out a $1M+ custom architecture.
HOW THE ON-PREM STACK SOLVES IT
The Shop Floor Bridge (Jetson)
Connects to all 12 vessel DCS controllers via OPC-UA. Reactor temperature, pressure, agitator RPM, pH, conductivity tags captured at full timestamp resolution. Zero internet egress.
The Right-Sized Core (RTX PRO 5000)
Runs batch genealogy, deviation workflow, and OEM customer audit-trail export inside the controlled perimeter. SHA-256 record hashes for tamper-evidence. OEM auditors satisfied on first review.
10-Week Cutover
Pilot live on 4 vessels in week 7, full cutover by week 10. OEM contracts preserved. Annual OEM audit cycle passed clean on the first run.
THE RESULT
Live in 10 weeks at $245K all-in. 2 OEM contracts preserved. $18M annual revenue protected.

Frequently Asked Questions

The most common questions SME plant owners, IT leads, and operations directors ask when planning the SAP MII migration with limited budget and team capacity. Talk to our SME migration support team.

Is there a real SAP MII migration path under $300K total cost?
Yes — for single-site SME manufacturers with 20-60 MII transactions and mostly standard usage. A right-sized iFactory deployment with Jetson + RTX PRO 5000 hardware, perpetual platform license, integration partner time, and 8-12 weeks of project work typically lands in the $150K-$280K range. The path that breaks the SME budget is mapping enterprise SAP DM economics onto SME scale — that quickly reaches $700K-$1.2M. The right answer is choosing a deployment model designed for SME constraints from the start, not a stripped-down enterprise plan.
Do we need a full DGX Station for an SME plant?
No. The DGX Station GB300 makes sense for multi-plant manufacturers training fleet-wide AI models on terabytes of historical data. A single SME plant is usually well-served by Jetson AGX Orin (for shop-floor connectivity) plus an RTX PRO 5000 or RTX PRO 6000 tower (for MES, OEE, predictive analytics). Total hardware footprint: one cabinet on the production floor plus one tower under a desk. DGX can be added later as a fleet upgrade if the business grows to multi-site.
How much can our existing MII work be reused versus rewritten?
For an SME plant with mostly standard MII usage, 70-85% of existing assets can be reused as configuration rather than rewritten. Tag mappings, KPI definitions, dashboard layouts, and PI/DCS connection profiles port as configuration — not code. Custom BLS transactions and Java enhancements typically need redesign, but most SME plants have very few of these. SAP DM by contrast requires clean-core API redesign of all custom logic — which is why the SAP DM path is so much heavier for SMEs.
What happens if our S/4HANA upgrade is happening at the same time?
Common SME situation — and it actually argues for moving MII off SAP early rather than later. The iFactory platform integrates with both legacy SAP ECC and S/4HANA via standard OData, RFC, and IDoc interfaces. You can complete the MII migration first (decoupling shop floor from the ERP timeline) and then run the S/4HANA upgrade against a stable manufacturing operations layer. Or both can run in parallel with a coordinated cutover. The integration partner handles the dependency mapping during the 4-week discovery phase.
How fast can we get a pilot live?
Typical SME timeline: Weeks 1-2 — discovery, MII inventory, OPC-UA tag confirmation, scope freeze. Weeks 3-4 — hardware delivered and installed, integration partner on-site, MII connections ported as configuration. Weeks 5-6 — first use case live (typically OEE or downtime tracking), operator training on the new dashboard. Weeks 7-8 — full cutover, MII moved to read-only or decommissioned. Total contract signature to fully-live: 8 weeks for plants with 20-40 transactions, 10-12 weeks for plants with 40-80 transactions or regulated workflows.
SME Edition · 8-12 Weeks · Perpetual License
Migrate Off SAP MII Without Stretching Enterprise Math to Your Plant.
Book a 30-minute call with our SME deployment engineers. Walk through your MII estate, your 1-3 person IT capacity, and your budget ceiling. See the right-sized fast-track plan live. Pilot in 8 to 12 weeks. Buy it once, own it forever — no monthly fees, source code included.

Share This Story, Choose Your Platform!