The CaseMap SQL Import Utility allows you to migrate local cases to the CaseMap Server. During the import process, the utility converts a case in an Access database format to a SQL Server database format. It creates a brand new SQL case and copies all information from the old case into the new one. You will also have the option to create the new case on a specified server instead of using an existing one. CaseMap cases can be converted individually or bulk imported to the CaseMap Server.  Duplicate cases will not be added to the list.

Once a case has been successfully imported to the CaseMap Server, the file extension on the local case is changed to ".001" to ensure that case staff can no longer open it in the client application. If a case already exists with the same name and extension, the numbers will increment to ".002" and ".003" to ensure a unique name.

You can also import a list of cases from a text file. The text file containing the list of cases must list one case per line. Each line must contain only the full path to the case file. The import utility will not add duplicate cases to the list.

When initiating the import process, you must use the administrative credentials you use in the SQL Server Properties dialog box in the CaseMap Admin Console. The CaseMap Administrative Credentials need to be filled in before you can import cases. This login must have the Create any database permissions on the specified SQL Server. This login will also become the database owner (dbo) for each imported CaseMap case.

Once the import process completes, a message box displays listing the number of cases successfully imported and any cases that failed to import. If you cancel the import during processing, CaseMap Server will finish importing the last case being processed before stopping. A list of all cases successfully imported displays on the Results tab in the CaseMap SQL Import Utility dialog box.

After the case is imported, it's important to verify case users and assign them to roles in the CaseMap Admin Console. See About roles and users.