If you are using StreamServe for document generation and distribution, you might have heard that StreamServe gained a wide range of functions and passed some important milestones in its development and branding in the past couple of years. StreamServe support lifecycle ended in June 2020. And we decided to clarify the situation for you, and explain what happened to the product, how you can upgrade to the latest supported version, and what StreamServe replacement options you have.
StreamServe History Overview
StreamServe has always been one of the top players in the Customer Communications Management market. Founded in 1997 in Sweden, StreamServe gained very quickly a strong customer base due to its many and tight partnerships with leading ERP, CRM and supply-chain solutions providers, such as Adobe Systems, IBM, InfoPrint Solutions Company, Lawson, and SAP, and the solution gained a decent customer base. (Did you know? a significant part of StreamServe product development, support and professional services was delivered by our team members before they joined Ecodocx).
Mostly because of it’s tight integration into SAP (nowadays marketed as Document Presentment for SAP Solutions), StreamServe was acquired by OpenText™. Back then OpenText™ and SAP already had a strong partner relationship. Like OpenText™, StreamServe had an established reseller partnership with SAP making it a natural fit with OpenText™’s SAP partner strategy.
Over the past two decades, StreamServe gained a wide range of functions and passed some important milestones in its development. The product was merged with other solutions, and a few times rebranded. This caused some confusion among customers.
In 2015, StreamServe was combined with newly acquired PowerDocs, a cloud-based tool for creating customer documents, and was called Customer Communications Management, or CCM. While StreamServe was best used for batch processing, PowerDocs was designed for on-demand output management and had tight integration with MS Word and Salesforce. The StreamServe part was renamed to Customer Communications Enterprise (CCE), and the PowerDocs part was renamed to Customer Communications CRM.
In 2016, OpenText™ acquired one of it’s biggest competitors in the CCM space – HP Exstream. As a result, OpenText™ introduced Exstream 16.2, a next-generation Customer Communications Management platform, combining the best features from Customer Communications Enterprise (StreamServe and PowerDocs) and Exstream (formerly HP Exstream).
In 2024 OpenText Exstream was renamed to OpenText Communications.
Today, OpenText Exstream ( now OpenText Communications) is actively used by more than 5,000 customers in 130 countries, primarily in the financial services, utilities, manufacturing, distribution and telecom sectors. Customers include BMW, Siemens Financial, AmerisourceBergen, FWD Life Insurance Company (Bermuda) Limited, L’Oreal, KPN, TMVW, du, IWB, Sysco, New York Life Insurance, Enkla Elbolaget, IT-Power, SourceGas, Irish Dairy Board, Marel, Media Logistics, DONG Energy, SSAB, Blokker, Merrill Lynch, Northshore Credit, Humana, Aviva Insurance, Penn National, Unum, RDS Group, Denver Water, E.On, Powergrid International Whitepaper, and many more. OpenText Exstream main technology partners include SAP, Salesforce, Infor, Oracle, Guidewire, Duck Creek.
OpenText StreamServe Replacement Options
1. Upgrade StreamServe to Exstream (Server-based)
StreamServe customers using version 5.6.2 or older can upgrade to the Exstream (Server-based) release (see table below) and enjoy the best of both platforms—leveraging both StreamServe and Exstream components. This approach allows customers to continue using familiar designers like StoryTeller and PageOut, while slowly migrating to the Exstream platform.
However, it’s important to note that creating new PageOut templates will no longer be possible. The transition to the Exstream platform can be done gradually, for instance, during future bill or letter redesign projects.
Manual migration of all forms and applications isn’t necessary. Customers can streamline the process using tools like the PDF Importer and other template migration solutions, enabling a semi-automated migration experience.
Interested in learning more? Contact us to explore the StreamServe to Exstream (Server-Based) migration tools and automation options. Let us assist you in planning and executing your migration project with ease!
2. Upgrade StreamServe to Exstream (Cloud Native)
StreamServe customers now have the opportunity to upgrade to the Exstream (Cloud Native) release. This modernized platform integrates thick-client (Designer and Design Manager) and thin-client (Communications Designer and Content Author) document design applications. Exstream (Cloud Native) can run in your company’s data center, in your cloud of choice (AWS, Azure, OpenText Cloud, etc).
While the goal is to maximize the use of thin-client applications, we at Ecodocx came across specific customer requirements, particularly in the utility sector, that are still best addressed using the classic desktop thick-client tools. However, OpenText is continuously and very actively enhancing the thin-client applications, and we expect the thin-client applications will soon match or surpass the capabilities of the traditional desktop solutions.
The migration process to Exstream (Cloud Native) can be largely automated using tools such as the PDF Design Import, DOCX Importer, and the API-based Private CommsMigration SDK. It’s worth noting that the Private CommsMigration SDK is not a tool that customers can use. It’s a migration approach that is only available when hiring OpenText Professional Services and select partners.
Want to learn more? Contact us to explore the migration tools, automation options, and expert support available for planning and executing your StreamServe to Exstream (Cloud Native) migration. Let us help make your transition seamless and efficient!
Integration Options
Both OpenText Exstream (server-baed) and OpenText Exstream (loud native), offer out-of-the-box integration with OpenText products, such as OpenText EIM repositories, Content Server, and Archive Server. Besides integrations into OpenText products, Exstream engine offers integrations with many market-leading applications in the insurance industry, such as Duck Creek Technologies and Guidewire InsuranceSuite, as well as electronic signature applications, such as DocuSign. In addition, OpenText already released an SAP integration package, which includes the integration with SAP business processes, including embedded interactive document creation in SAP S/4 HANA and SAP C4C. The out-of-the-box integration with SAP applications is available when Exstream is purchased as part of the Document Presentment for SAP Solutions package.
Talk to us
Don’t hesitate to connect with us to schedule a one-on-one meeting with one of our experts about your specific business needs. We would be happy to advise you on StreamServe upgrade or replacement options. Contact us today.
Disclaimer: All product and company names are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them. Ecodocx gives no warranty and accepts no responsibility or liability for the accuracy or the completeness of the information and materials contained in this website. Under no circumstances will Ecodocx be held responsible or liable in any way for any claims, damages, losses, expenses, costs or liabilities whatsoever (including, without limitation, any direct or indirect damages for loss of profits, business interruption or loss of information) resulting or arising directly or indirectly from your use of or inability to use this website or any websites linked to it, or from your reliance on the information and material on this website, even if Ecodocx has been advised of the possibility of such damages in advance.