1. create a eBiss Folder Backup(exclusive Message Store)
2. Determine MessageStore Location
3. Create list of all active HardDisk Channels
4. Create list of all http channels and ports
5. Create list of all SMTP/POP channels
6. Create list of all active EventListeners
7. Determine name and IP of existing server
8. Determine name and IP of new server
9. Determine the location of the future eBiss installation
10. Determine the Location of the Future MessageStore
11. Determine the future locations of the HardDisk Channel paths
12. Determine user of eBiss service (if != system account)
13. Get current SQL-Connection String for the eBiss database instance¹⁾.
14. If necessary, leave network drives on new server folders.
15. if necessary, determine future database server
16. if necessary, determine firewall settings
17. If necessary, determine Active Directory user rights.
18. for partner integrations via FTP/SFTP on remote server: check if new client IP is allowed for login to partner.
19. Check the Windows server region and language settings. If possible transfer them 1 to 1 to the new server. Otherwise it can cause undesired effects when converting strings to date or numeric values in mappings, if the corresponding functions²⁾ were not applied correctly or an automatic type conversion must be done³⁾.
20. eBiss configuration check for custom settings⁴⁾ such as:See:MapCustomTypeId⁵⁾
21. Check if the eBiss Webgui is used with a custom plugin⁶⁾. This must also be moved to the new server.

1. Deactivate active event listers and save settings
2. Stop and deactivate eBiss service
3. Copy eBiss Folder Backup to new location
4. Copy Message Store to New Location
5. Only with a new database server ⁷⁾:
   1. Create database dump with suitable tool (e.g. SQL Server Management Studio) or DBCopy
   2. Establish new database instance and import previously created dump.
   3. If necessary, determine or create a new database user⁸⁾
6. Run eBiss.Configurator.exe in new location and parameterize with new database account details and server name/IPv4 address if necessary.
7. if necessary set up and start eBiss service with system account or the previously used account⁹⁾.
8. Create shortcut for eBiss.WinClient.exe on desktop
9. Start eBiss Client on new server
10. if necessary correct and save all Hard Disk Channels with new path information
11. Activate deactivated event listeners
12. ensure that eBiss shortcuts are updated on the PC clients and work.
13. make sure that FireWall rules on the PC clients are not in the way to display the TraceLog.
14. Make sure that all plug-ins have been taken over.
15. Make sure that the old Windows service of eBiss 2 has been deactivated / uninstalled.

Note: We recommend a so-called SA account when using MS-SQL Server. This is specified in the configurator for the authorization of the eBiss database instance. (Integrated Security also works, of course, but requires that the account under which the eBiss service is running has the appropriate database rights. )