Lansweeper — Migration Reference

Lansweeper — Migration Support Overview

Role in migrations

• Staff (HD): supported as source.
• Company (HD): supported as source.
• Contact (HD): supported as source.
• Ticket (HD): supported as source.
• Category (KB): supported as source.
• Folder (KB): supported as source.
• Article (KB): supported as source.

Field-level support migrating FROM Lansweeper (Ticket)

Field-level support migrating FROM Lansweeper (Company)

Field-level support migrating FROM Lansweeper (Contact)

Field-level support migrating FROM Lansweeper (Article)

Migration options available for Lansweeper

• Select records for Demo - applies to: source (Ticket)
• Skip ticket attachments - applies to: source (Ticket)

Lansweeper — Setup & How-To Guide

For more information: https://help-desk-migration.com/help/lansweeper-migration-guides/

How to Create a Data Backup in Lansweeper to Migrate Your Data?

To migrate data from Lansweeper using the Migration Wizard, you need to follow these steps to back up your database:

1. If you don't already have Microsoft Visual Studio installed on your computer, download and install it from the official Microsoft website.
2. Install SQLite/SQL Server Compact Toolbox Extension:
   1. Open Microsoft Visual Studio.
   2. Go to the "Extensions" menu and select "Manage Extensions."
   3. In the Extensions and Updates window, search for "SQLite/SQL > Server Compact Toolbox."
   4. Download or install the extension.
   5. Follow the on-screen instructions to complete the installation.
3. Launch Microsoft Visual Studio and open the Server Explorer.
4. Add a Connection:
   1. Click the "Tools" button in Visual Studio.
   2. Open the "SQLite/SQL Server Compact Toolbox."
   3. Select "Connect to the database."
   4. Enter the server name and database name as  "Lansweeper.db."
   5. Test the connection and click "OK" to add the server to your connection list.
5. Click the "Add SQL Server connection" button in the toolbox. Select the server you created earlier and add it to the toolbox.
6. Migrate to SQL
   1. Right-click on the connection name and choose "Migrate to SQL."
   2. Select all the tables you want to migrate and click "OK."
   3. Helpdesk tables start with htbl (i.e., a table with teams would be called htblteams, a table with users would be called htblusers, etc.). Here is a list of required tables:
      1. htblteams
      2. htblusers
      3. htblagents
      4. htblticket
      5. htblticketcustomfield
      6. htblticketteam
      7. htblnotes
      8. htblpriorities
      9. htblticketstates
      10. htblsource
      11. htbltickettypes
      12. htblcustomfields
      13. htblcustomfieldvalues
      14. htbltickettypecustomfield
      15. htblattachements
      16. htblfiles
7. Name the file (e.g., "lansweeper") and save the dump to your computer.

Note: Ensure that the dump file has the proper structure, with a folder named db containing the lansweeper.db (file).
Keep in mind that you will not be notified about the end of the import. However, there are two signs to look for to make sure your dump is ready to be used:

• The size of your dump remains stable for a long time;
• You see only one file in the db folder instead of two.

1. Export Attachments:
   1. Navigate to the "C:\Program Files (x86)\Lansweeper\Website\helpdesk\files" directory in your Lansweeper installation directory.
   2. Compile all attachment files along with the database dump file into a single ZIP file.
2. Upload Backup File to Migration Wizard:
   1. Go to the Migration Wizard and look for the option to upload your backup file.
   2. Upload the ZIP file containing both the database dump and attachments.
   3. Click the "Continue" button to establish a connection between the Migration Wizard tool and the backup file.

Alternative Backup Access and Format Conversion

If the client can't upload the backup to the tool directly, they can instead give us access to it via a file-sharing resource, and we'll download it ourselves.

The tool only accepts the database backup in .db format, and Lansweeper doesn't always allow downloading a backup in that format. If the backup isn't available in .db format, it can be produced as follows:

1. Extract the tables from the .mdf database in SQL format.
2. Create a SQLite database and import those tables into it, then save it — this produces a file with the data in .db format.