Blog

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.