Blog

Document sprawl across multiple silos effect every organization.  According to AIIM, 52% of organizations have three or more document or content systems another 22% have five or more systems.  Most of these content repositories don’t talk to each other forcing users to work across multiple applications to access the documents they need to perform their daily jobs.  This sprawl has resulted in additional costs and risks to these organizations. 

Here are three reasons to address document sprawl.

As organizations move to new platforms to manage their documents, services in the cloud are a huge part of the solution.  Amazon Web Services (AWS) provides several ways that Enterprise Content Management (ECM), Content Services Platforms (CSP) and, Document Management Systems (DMS) can use to store content in the cloud.  The Simflofy Content Federation Services platform supports many of these approaches.

Most organizations do not have a handle on their content.  Documents can be stored in various locations.  An organization’s invoices may be in a capture platform.  Its contracts may be in a Contract Lifecycle Management (CLM) or Enterprise Resource Planning (ERP) system.  And its employee documents may be sitting in an On-Boarding solution or Document Management System.  According to AIIM (the Association for Intelligent Information Management) most organizations have over five different repositories, varying from file systems and network share to Enterprise Document Management platforms.  Just finding documents can be difficult.  But is finding enough?

Strategic partnership enables organizations to connect to all of their disparate stores of content without the  cost, pain and risk of migrations

New York City, NY – Sept. 21, 2017: Nuxeo, maker of the leading, cloud-native content services platform, today announced a strategic partnership with Simflofy, provider of Content Integration Services. The partnership enables Nuxeo’s customers to intelligently meet their ECM objectives by connecting to content where it lives, whether in legacy enterprise content management (ECM) systems or business applications, and removes the cost, pain and risk of content migrations typically associated with ECM implementations.

No, we have not gone crazy.  Think about it, you know you’re going to move off of your old content store to a new platform.  The old system just doesn’t do it, if there ever was one in place.  You may not know how much of the content is ROT documents (Redundant Obsolete or Trivial).   You may not know how many documents there are out there to be stored.  So you start the selection process for a new vendor with many unknowns.  But these unknowns are quickly answered once you start your migration.  What if you could find out these answers first?

Gone are the days when a document migration was as simple as running a file dump and a script to load the new repository.  Spending four to six weeks creating the scripts to custom load your document collection and then several trial and error attempts to move thousands, or at most a few hundred thousand, documents wasn’t trivial but was common for most migration.  Today’s migrations are usually about billions of documents being stored in several different sources and sometime being moved to several destinations.  Yesterday’s migration solutions don’t address today’s migration challenges.

One of the questions we are often asked is, “Wouldn’t a company just migrate content?”  It seems a straight forward issue.  If an organization has various enterprise content management (ECM) and document management systems (DMS) platforms, wouldn’t it just make sense to migrate content off lesser used legacy repositories.  Sometimes this is not possible.  International organizations must deal with Data Sovereignty and Residency, a requirement by certain governments to maintain Personal Identifiable Information (PII) in repositories within its geographic boundaries for that country’s citizens.

One of the most common questions we get from our vendor prospects is, “Why should we use your platform when we can build it ourselves?”  They are right, they may be able to build a basic point integration themselves, but why should they? ... Sure you could have your development team build integrations but doesn’t your development team have more important things to focus on?  The Simflofy team’s main focus is content integrations.

As partner technology to any vendor, we’ve all been there.  We all once had “that” sales call.  It was a great sales call.  The customer loves your solution.  You have shown them how your solution can solve their problems.  Then the dreaded question, “But does your solution work with Vendor B?”  Your brain goes on overdrive.  Can we?  Can’t we?  Your hesitant response, “No, but I don’t see why not.”

Simflofy has been building integrations for five years and has proven in production integrations to …
Alfresco, Box, DocuWare, Dropbox, Google Drive, Hadoop, IBM Content Manager, IBM Filenet, Microsoft Sharepoint, Microsoft Sharepoint Online, OpenText Content Server, OpenText Documentum, OpenText LiveLink, Salesforce, Xerox DocuShare, and even FTP and the file system.