Preliminary planning for implementing any software application is important for achieving the best set-up results, the first time. We recommend that you take some time to review and plan how your organization will be using CaseMap, especially if you are also installing the CaseMap Server, the CaseMap Admin Console, and the CaseMap SQL Import Utility. Planning ahead helps ensure that administrative tasks are minimized for initial setup and your long-term maintenance of the application and its companion products.
![]() | Plan before you install CaseMap |
Before installing CaseMap and the CaseMap Server, the CaseMap Admin Console, and the CaseMap SQL Import Utility, we recommend you review the following checklist to ensure you have not missed any steps in planning details.
|
Designing cases is a necessary planning phase that ensures consistency in structure, naming conventions, security, user permissions, etc. The more forethought you apply to designing case templates and user roles for implementing security, the easier it is for you and other administrators to identify any irregularities that may occur. Consistency is key when it comes to field naming conventions, use of field types, and spreadsheet field placement in CaseMap cases. When field guidelines are established, it is less confusing for users and administrators who are working in multiple cases. For more information, see Before creating cases and About cases. |
If you are using CaseMap Server, a migration path for importing cases from previous CaseMap versions is essential. You should only migrate a case to a CaseMap Server case once. If you experience an issue during the import, you can try migrating the case again. Each SQL case requires its own SQL database. For more information, refer to the CaseMap Server documentation. |
![]() |