OpenText StreamServe contract up for renewal? This page explains why evaluations are happening now, what a replacement involves, and where InterformNG2 fits - including where it does not.
Talk to an expertMany organisations still run OpenText StreamServe for business documents, often installed years ago alongside Infor M3, SAP or an IBM i system. StreamServe was built in Sweden and became one of the most widely deployed output tools in ERP environments, particularly Infor M3, where it was long bundled as M3 Output Management with the StoryTeller and PageOUT design tools. OpenText acquired StreamServe in 2010 and later folded it into its Customer Communications portfolio, first as Communications Center Enterprise (CCE), then under the Exstream brand.
Three published facts drive today's evaluations:
None of this forces an immediate decision. It does mean that staying put has a defined end point, and that the vendor-provided path leads to a full Customer Communications Management (CCM) suite. For many ERP-driven businesses, that path covers far more than they use StreamServe for - which is why an Output Management alternative is worth evaluating alongside it.
A StreamServe replacement is a well-understood project, not a leap. Four workstreams matter:
StoryTeller and PageOUT layouts accumulated over 10-25 years. Most environments carry far more templates than they use; migration starts by identifying what is actually live. InterformNG2 supports layout import from PDF files and transformation of older spool formats into structured templates, and consolidation is normal - customers have reduced 500 templates to 50.
The replacement must accept what your systems produce today: XML from M3, IDocs or structured data from SAP, and SCS or AFPDS spool files from IBM i applications.
Print, PDF, email, archive, EDI and e-invoicing routes must all carry over. Map every StreamServe output connector before the project starts, not during it.
Old and new environments run side by side until every document is validated. No cut-over risk, no disruption to daily operations.
Our migration of legacy output page describes the step-by-step approach in detail.
InterformNG2 is a dedicated Output Management platform. Output is all we do, and has been since 1987 - more than 4,500 installations worldwide, and our first customer is still active today.
Interform has been an Infor solution partner since 1999 and a complementary partner since 2025, with more than 500 Infor customers. When your needs go beyond IDM, InterformNG2 is the recommended output solution for Infor M3, delivered as a standardised M3 package with 150 out-of-the-box templates and workflows. Built for M3 CE and 13.4 using XML output; older stream-file based versions can be converted within Interform. Read more about Infor M3.
InterformNG2 runs natively on IBM i - no Windows client installations - and converts SCS and AFPDS spool files into structured output. If StreamServe sits next to an IBM i application today, the platform does not have to change. Read more about IBM i.
One output platform across SAP (without heavy SAP customisation), Microsoft Dynamics 365 (without custom development in Dynamics 365), Infor and IBM i applications. Mixed SAP and IBM i landscapes - the classic StreamServe estate - are exactly what InterformNG2 is built for. Read more about SAP.
InterformNG2 prepares and validates PEPPOL BIS, OIOUBL, XRechnung, ZUGFeRD and Factur-X, and hands the result to your PEPPOL access point. Mandate-driven e-invoicing is often the requirement that makes organisations look beyond their current output tool. Read more about e-invoicing.
On-premise, hybrid or cloud - the platform and templates stay the same when your hosting model or ERP version changes.
Buyers replacing StreamServe usually judge a new platform on five things. Here is where InterformNG2 stands on each, stated as facts about our platform - your own evaluation is the right place to weigh them against your current setup.
InterformNG2 prints natively on IBM i and gives predictable print performance whether you run on-premise or in the cloud, with a local print client for cloud ERPs. Output Continuity keeps documents flowing during ERP downtime or system failures.
Business users update layouts, logos and fields in the Intelligent Designer without ERP coding or developer time. Infor M3 customers reduce implementation time by around 70%, and most can manage output in-house after about one day of training.
One platform across Infor, SAP, Microsoft Dynamics 365, IBM i and other applications, with no ERP-specific development. Output stays consistent across a mixed landscape.
The same platform and templates run on-premise, hybrid or in the cloud. No redesign when your hosting model or ERP version changes.
PDF/A and PDF/UA, full Unicode including Chinese, Japanese and Korean, and e-invoicing formats: PEPPOL BIS, OIOUBL, XRechnung, ZUGFeRD and Factur-X.
Real-time monitoring of output workflows shows when something fails before it reaches the warehouse floor, with automated routing and archiving handled outside the ERP.
An honest fit assessment saves everyone time.
OpenText positions its Communications (Exstream) platform for large-scale Customer Communications Management - highly personalised, high-volume customer correspondence in sectors such as financial services, telecommunications and utilities. If your StreamServe use is primarily interactive correspondence and CCM-style customer engagement at that scale, the vendor migration path to Exstream, or another CCM suite, may serve you better.
InterformNG2 is the strong candidate when StreamServe's job in your organisation is ERP-driven operational output: invoices, order confirmations, delivery notes, labels, picking lists and compliance documents across manufacturing, distribution and logistics. That is the majority of StreamServe installations in Infor M3, SAP and IBM i environments - and it is what a dedicated Output Management platform does better than a CCM suite sized for banks.
For ERP-driven document and label output - the role StreamServe plays in most Infor M3, SAP and IBM i environments - yes. InterformNG2 covers design, workflow automation, distribution and archiving as a dedicated Output Management platform. It is not a CCM suite; if you need large-scale interactive customer correspondence, evaluate CCM platforms for that part.
There is no one-click import of StoryTeller or PageOUT projects, and a one-to-one copy is rarely the goal. InterformNG2 imports layouts from PDF files and transforms older spool formats into structured templates. Beyond that, we are happy to look at your existing StreamServe resources directly - individual elements can often be converted, and even where they cannot, they help us build the new setup faster. The migration process typically consolidates templates significantly, and the old and new environments run in parallel until everything is validated.
Yes. InterformNG2 runs natively on IBM i, handles SCS and AFPDS spool files, and connects to SAP without heavy SAP customisation. One platform covers both, plus any other applications that produce output.
Infor CloudSuite M3 delivers standard output through Infor Document Management (IDM). When your needs go beyond IDM, InterformNG2 is the recommended output solution for Infor M3, with a standardised package, IDM template conversion and 150 out-of-the-box templates and workflows.
No. Migration is stepwise: identify what is actually in use, move document types in stages, and run old and new outputs in parallel until validation is complete. Renewal dates make useful deadlines, but the project itself is phased.
Yes. It prepares and validates PEPPOL BIS, OIOUBL, XRechnung, ZUGFeRD and Factur-X, and hands documents to your PEPPOL access point. InterformNG2 is not itself an access point.
Talk to our team about what a phased, low-risk replacement looks like for your environment.
