How to migrate Dameware Central Server by exporting and importing server data

8/8/2022 3:39 PM

6/4/2026 9:43 AM

This article explains the recommended method for migrating a Dameware Central Server to a new server.

Migrating the Dameware Central Server database file (DamewareDB.sdf for older versions and DamewareDB.sqlite on later versions) is not recommended for a centralized Dameware migration. The cleanest approach is to perform a fresh installation on the new server, then export the Dameware Central Server data from the old or live server and import it into the new server.

This process does not require you to take the live server offline during preparation. The old and new servers can run side by side, allowing you to validate the new server before moving the Dameware license and placing it into production.

This article can also be used as a workaround when a Dameware Server upgrade fails. In that case, you can export the existing server data, uninstall Dameware Server, install the latest version on a clean server or the same server, and then import the exported data.

A newly installed server includes a 15-day trial period for testing.
For a temporary license for validation before production cutover, contact Customer Service through the Customer Portal.

Dameware Remote Support & Mini Remote Control

Dameware Local Users

• Export your Dameware Local Users
  1. Open Dameware Administration Console
  2. Go to Central Server > Users
  3. Select "CSV Export" from the Top Menu
  4. Save the CSV file in a safe location
• Import your Dameware Local Users
  1. Open Dameware Administration Console
  2. Go to Central Server > Users
  3. Select "CSV Import" from the Top Menu
  4. Select the exported CSV file

Dameware Users from Active Directory

• Export and import your Dameware Users if it is a sync from Active Directory.
  
  • There is no option to export these types of users as it's a sync from your Active Directory. The best way to export these users is to note the AD Group used for each user and their license type, then sync them to your Active Directory.
  • Make sure to inform your users to back up their Personal Host List before the migration
  • Import users from Active Directory into Dameware

Global Host List

• Export Your Global Host List
  1. Open the Dameware Administration Console
  2. Go to Central Server > Global Hosts
  3. Select the Root Folder and right-click to select "Export"
  4. Save the file in a safe location
• Import hosts to the Global Host List in Dameware

Saved Host List\Personal Host List

• Export Your Saved Host List\Export Your Personal Host List
  • This is a per-user task, so each of your technicians must do this on their own Dameware Mini Remote Client Machine. 
  • Reference: Manage the Saved Host List and Personal Host List in Dameware

Remote Host List

• If you use an Internet Proxy Server and rely on the Remote Host List for unattended Internet Sessions, that portion is not migrated through this process. A new server uses a new deployment link, and remote hosts must install the preconfigured agent from that deployment link before they appear in the Remote Host List.
  Ref: Invite a remote host to an unattended session in Dameware 

Dameware License

• Dameware License Offline Activation and Deactivation when Dameware Online Activation is Failing

Dameware Server New IP/Hostname

• Once the new Server has been created and the new server has a different Hostname and IP from the old one, it is required for Users to update their client connection.
• To do this:
  • 
• If the old server is decommissioned and the new server inherits the old server's Hostname and IP Address, then no need to change on the user side.

Dameware Server Default Certificate

• A new server means a new Dameware Signed-Certificate.
• All users, when connecting to the new server, will get this prompt and need to accept the new Dameware Signed-Certificate.
  • 
  • 
• For customized Port 6133 certificate, please refer to this article: Dameware: How to change the bound certificate