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?
Because Simflofy is a federation AND migration platform, we can create a migration to any repository, even a temporary location or none at all. Use Simflofy’s Discovery feature to find all of the content types and attributes stored in your existing systems. Create migration jobs and test expected attribute mappings. Find out how many of your documents are duplicates. Get a count of how many documents you’ll be bringing into the new system. Find out where your expected type matching doesn’t fit the stored content. You can do all of this by running a test migration first. Then once you’ve installed the new repository, point Simflofy at it and start your migration.
Go ahead and take your time choosing the right content platform. Then when you’re ready, just run your Simflofy jobs again to migrate your content 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
…from any of those repositories.