If you’re in the process of migrating to a newer version of Microsoft Office, then you’re liekly trying to figure out what you don’t already know about the challenges of the process.
In this blog, we’re going to discuss file remediation and the troubles you stumble upon when migrating your platform. Thinking about previous stages, planning is where you identify files, getting an idea of how many files there are out there, what types and so on. Then you identify which are potentially problematic: we estimate about 10%. But how do you identify precisely the files that will need fixing afterwards?
This is where OfficeConverter comes into play. The solution not only identifies which links are not working and why. But it also analyzes the actual VBA code of the file. It looks for the long list of commands that either no longer work, or continue to function but may behave a little differently. In many cases it can modify the code automatically. The ones that cannot be fixed automatically, the solution will point out the actual line of code that is broken so IT can go and manually remediate these files. The OfficeConverter scanner will give a detailed explanation for which documents won’t update and why. It will tell you which module it’s in, which line in that module and in most cases it will be able to automatically fix the code. It has a reporting tool that can generate a report of every file that has a link and the files it links to, as to keep these together. So then you have a definitive course of action, because you’ll know what you have to do next. Our recommendation is to go with the automatic solution. This solves your budget and time problems, IT will be happier, as they won’t have to manually go through all the links.
OfficeConverter can scan and remediate a Word document in 5 to 7 seconds, and Excel spread sheet in roughly 10 to 15 seconds and an Access database in 30 seconds to a minute. OfficeConverter fixes 90 to 95% of the broken files. The rest of 5 to 10% are usually business decisions that OfficeConverter cannot and shouldn’t fix automatically.
For example some functionalities won’t be in the next Office version. So businesses need to make a decision regarding these: do they move them to the cloud, do they use another Office Suite program and so on. OfficeConverter can also leave the broken line of code in the file, after fixing it. This is a good training tool for IT as well. It also leaves a trail of fixes, visible for auditing or any verifications.
We remove the unknown for you: we let you know which files won’t work and why. It saves you time, money and it makes your employees happier and more productive.