1

Updated instructions: https://community.spiceworks.com/support/desktop/troubleshooting/moving-spiceworks-desktop

This how-to will show you how to transfer your Spiceworks database from one machine to another. Let’s say you have Spiceworks installed on your own computer as you’re learning how to use it, but now you’re ready to add additional users. In this case you’ll probably want to move Spiceworks to a server to give them access at all times. Rather than having to reconfigure Spiceworks and figure out all your unknowns again, you can just move your entire database and save yourself a lot of trouble.

NOTE: If you are updating and run into an issue where the migration won’t complete, it means Spiceworks has discovered issues with your database that need to be repaired. Please contact Spiceworks support to have your database repaired.

NOTE: There are slight differences to the process depending on whether you are moving a stand-alone installation, a remote collector or a central installation. All the directions below pertain to a stand-alone installation with the alterations noted for each other installation type.

Step 1: Create A Backup Of Your Database

Backup_02.png

Navigate to “Settings > Global Settings > Backup Configuration”. Select a backup location, or note the default location so that you can later retrieve your backup files. Click “Backup Now”.

Step 2: Install Spiceworks On The New Machine

Backup_06.png

Download and run the Spiceworks installer on the new machine. If at all possible, try to install Spiceworks in the same directory and use the same port as the machine your original installation was on. If given the choice to Run Spiceworks Now, do not do so.

DO NOT complete the registration process.

Step 3: Exit Spiceworks

Backup_04.png

If Spiceworks is running, stop Spiceworks by right-clicking the system tray icon and selecting “Exit”, or, if Spiceworks is running as a service, stop the service.

CENTRAL INSTALLATION: You also need to take all of your Remote Collectors offline to be absolutely sure you don’t miss any tickets/updates.

Step 4: Delete Database Information

Backup_05.png

Navigate to the Spiceworks directory on the new installation and delete the “data” and “db” folders.

Step 5: Transfer Your Backup To New Installation

Backup_03.png

Find the zip file created when you backed up Spiceworks and extract the “data” and “db” folders contained within. Move these folders into the new Spiceworks installation’s folder. When you start up Spiceworks next, your old database will be waiting for you.

REMOTE COLLECTORS: You need to completely uninstall Spiceworks from the old location before bringing the new installation online. It is very important that your Spiceworks installation from the old location never be online at the same time as the new location. Once you bring the Remote Collector back online in the new location, it should connect to your central installation automatically.

Step 6: Central Installation Additional Step (for Remote Collectors & Agents)

First, bring your Central Installation back online. Then start up your Remote Collectors and Agents again. Now you’ll need to access each of the Remote Collectors and Agents, and then update the host name or IP Address that they use to access your Central Installation. Once you get those updated, the Remote Collectors and Agents should connect again without you having to enter the authorization code again.

Step 7: Recreate your Backup Settings

All of your settings will stay intact when you move your installation, except the backup settings. They revert to default. If you have customized your backup, you’ll need to update this after you perform the move.

A lot of people need to change their installation location at some point. If you’re one of these, hopefully this document helps to make it as painless as possible. We know you don’t want to have to deal with all those unknowns and scan errors again.

1169 Spice ups
2

Thanks!

3

I haven’t run into it, yet… but what should be done if you can’t setup the new installation on the same path as the old installation?

4

This is exactly what I am looking for, and it looks pretty easy. Thanks!

5

ok, very good. thanks

6

Great this is exactly what I need. We installed it on a local machine to try it out and now want to move it onto one of our servers. This will make sure I don’t mess anything up!

7

Perfect.

8

You are my savior, man! I just finish migrating, work excellent :slight_smile:

9

Is there anything you need to do if you move it to the 4.0 version?

10

This also works great if you have repaired or modified a database and need to get it back up and running.

11

TNX! I’ve decided to test spiceworks on my own PC. But now I’m thinking it’s worth server installation)))

12

We had to do this recently, I didn’t know about this post. I just went to the backup folder and extracted the two zip files just like noted here and it worked flawless. I thought there might be a problem with the PC name change, but all was well.
Thank You for making it easy like that.

13

Like, r1j1k, I installed it on my laptop first, but will need this to migrate to a server when I officially start using it. Cool beans!

14

Thanks for this - just what I needed once I realised how good spiceworks was, I knew it needed to move to one of our servers from the test installation.

15

Brilliant! saved me some major headaches! Just moved it to server without a problem.

16

Thanks for this, great how-to, will be needing this when I transfer Spiceworks from my PC to the Server. Very useful!

17

Extremely great to know that a product such as Spiceworks can be moved fairly easily.

18

I will be moving the installation and cannot use the same filepath. What issues will ther be and are there workarounds or fixes?

19

Thanks Jonathan, exactly what was needed and worked like a charm!

20

Worked perfectly! Thanks!