However, extensive tests are required to ensure that the system is fully Year 2000-compliant. If the manufacturer of the software has a version that is Year 2000-compliant, you can upgrade to that version. If a compliant version is not available or is too expensive, you can replace the non-compliant software with a completely new system. If you've been wanting to replace older systems, the Year 2000 may provide you with a good reason to do so right away. Of course, when you replace existing software, you often must convert your data to the format used by the new system, so that is another cost that must be considered.
Many companies have older software that is being underutilized.
In the case of custom and customized software, you may still need the capabilities of the system but do not have the time or budget to replace the non-compliant software. In these cases, you must repair the software. In other words, you must correct the errors and make the software fully Year 2000-compliant. Once the source code has been modified to correctly handle the Year 2000, it must be tested thoroughly before it is made available to users. This step is very time-consuming, and if your systems are not repaired soon enough, you will not have time to finish ironing out the bugs before the software must be placed into use in a production environment.