CaseMap continues to allow you to convert previous version cases to the new current release version. For example, you can upgrade a CaseMap v8.0 case to a CaseMap v9.0 case and have it still write to a Microsoft® Access database. Use the CaseMap SQL Import Utility to migrate local cases to SQL cases.
When upgrading a previous version case to a new version, CaseMap recognizes the older case format, such as a CaseMap v8.0 file (.cm8 extension) and offers to convert it to the new version format for you. It only takes a minute or so to convert previous cases to the new CaseMap format.
During the conversion process, CaseMap does not change anything in your existing CaseMap file. It creates a brand new case and copies all information from the old case into the new one. Additionally, CaseMap changes the file extension of the older version, such as .cm8 to .001. This change keeps users from inadvertently reopening the old case and using a previous CaseMap license.
If a case already exists with the same name and extension, the numbers will increment to ".002" and ".003" to ensure a unique name. We recommend that you inform case staff when the import is complete and that the original case is now renamed.
Previous versions of CaseMap are not used during the conversion process, so you can uninstall them at any time. |
Once a case has been converted to a new version format, users can no longer access it using an older CaseMap version. We recommend that all users get new versions installed at the same time. |
The message box displays the directory location of the original case and its new file extension. The Case Logon dialog box now displays and you can open the case in the current version of CaseMap.
|
![]() |