About migrating cases
Contents
CaseMap and TextMap support creating both local and SQL cases. You can easily migrate a local case to a SQL database that is managed using the CaseMap Admin Console.
To migrate existing cases, see:
Before importing SQL cases, we recommend you set up CaseMap Server users with assigned roles in the CaseMap Admin Console. The import process will automatically import case user assignments when the local case users match the CaseMap Server users you have created. You can still map users that don't match up automatically. See About roles and users.
Once users are mapped they should automatically be assigned to the SQL case and able to open it in the client application. For more information, see Mapping case users.
|
Always backup copies of the local cases before you migrate them into CaseMap Server. |
|
Previous version SQL cases can now be upgraded in the CaseMap Admin Console to receive the latest update or version of the client application: CaseMap or TextMap. See Upgrading cases. |
Microsoft SQL Server is a widely available client/server relational database system. Microsoft SQL Server provides several benefits to CaseMap Server:
|
The first key to a successful migration is having your organization's SQL Server Database Administrator work with you in this process. Since each organization's needs are different, the SQL environment tends to be uniquely configured. Involving your SQL Database Administrator will help save you time and effort. The CaseMap Technical Support team does not have knowledge of your SQL configuration and therefore, cannot answer your SQL questions. However, they can help you with your CaseMap, TextMap, CaseMap Server and CaseMap Admin Console questions. When calling the support team, please make sure your SQL Database Administrator is on the call to answer SQL configuration questions from support. |
 |