Home > SIX 2013 Documentation > Administrator Guide > Installing SIX > Upgrading from SI5.5

Upgrading from SI5.5

Overview

 

This explains upgrading from SI5.5 to SIX.

Details

 

File:SIX_Guide/002_Installing_SIX/007_Upgrading_from_SI5.5/si5_to_six.jpg

 

Yes, it is time. Farewell SI5. 

 

You will still go through all of the steps for installing SIX as a new user would. SIX does not overwrite SI5.5, it installs separately. There are functions for converting your SI5.5 Product Data (Catalog and settings) and your SI5.5 Projects.

Legacy Data Conversion

 

I know, it seems that just yesterday SI5 was released and now it is being called legacy...

 

There is a function for converting and importing your SI5.5 Product data to SIX. On the machine where you installed your SIX Server you will find it under your Windows menu at All Programs->D-Tools SIX->SIX Legacy Data Conversion Utility:

 

File:SIX_Guide/002_Installing_SIX/007_Upgrading_from_SI5.5/six_legacy_data_convertsion_utility.jpg

 

You can also access the Legacy Data Conversion (LDC) Utility via the Control Panel if you are logged into the SIX Client on the same machine where your SIX Server is installed.

 

Make sure that you synchronize your SI5 data from an SI5 Client to your SI5 Server prior to running the LDC.

 

This will open the D-Tools SIX Legacy Data Conversion Utility form:

 

File:SIX_Guide/002_Installing_SIX/007_Upgrading_from_SI5.5/d-tools_six_legacy_data_converstion_utility_form.jpg

 

Here you will point enter in the path to your SI5.5 SQL Server in the format MACHINENAME\SQLSERVERNAME. The default SQL name for SI5.5 is shown above: DTOOLSV5

 

You will also want to map to where your SI5.5 server folder for Products is located. This folder holds your SI5.5 Product images. This is generally on the same machine running your SI5.5 Server and the default path is shown above: C:\DToolsData\Products

 

If you did not use the Express option when configuring your SI5.5 Server, and instead used the Custom configuration, you will likely need to change both of the defaults above to reflect the paths you chose for your SQL Server and Products folder.

Duplicates

 

 

Your SI5.5 database could possibly contain duplicate Items, same Manufacturer and Model, but different Categories. You can choose to just "Convert the last updated duplicate product" which will only import the most current duplicate product.

 

You can also choose "Export duplicate products to CSV". This will create CSV file that you can then open in Excel and review. If you find that you want to import any of these duplicates, you can do so with our Import function.

Remarks

 

Once your SI5.5 database has been converted and imported into SIX, you will need to close SIX and re-launch for your Images, Company Information and Logo to populate in SIX.

Converting SI5.5 Projects

 

To convert an SI5.5 Project to SIX, use the Import Project function.

 

We recommend finishing any existing Projects in SI5, then convert them to SIX for future viewing/revisions.

 

The SI5.5 project will be copied and converted to the SIX format. Once converted, a SIX project can NOT then be converted back to SI5.5 format, but that is why we copy the SI5.5 Project vs. moving the Project. In other words, any Project you convert will still exist in SI5.5.

 

Converted SI5.5 Projects will retain any Revisions for the Project but no Sales Orders (SOs don't exist in SIX), Tasks, and Work Orders will not be converted to SIX.

 

Note: The total price of your project will likely be slightly different once imported into SIX. This is due to a change in how the estimated tax is calculated. In SI5, tax was calculated and rounded on a per Item basis, which caused mismatches when exported to third-party software like QuickBooks. In SIX, the sub-total of all Items is taxed, then rounded.

Best Practice

 

There is no "bulk" conversion feature for SI5.5 Project, they must be converted one by one. The easiest way to convert an SI5.5 Project to SIX is to Check Out the Project and convert the local (vs. server) copy of the Project. This is because local Projects are stored in an easy to read folder structure of CLIENTNAME\PROJECTNAME. Projects that are on the server (Checked In) are stored in folders named with a GUID, e.g. d2674ca6-f883-46f5-8f3e-b1ec4c5eac2e.

 

The instructions below assume that you have an SI5.5 Client and SIX Client running on the same machine. If that is not the case, in step two you can copy the Projects from your SI5.5 Client to the machine running a SIX Client for the conversion.

 

  1. Check Out the SI5.5 Project. The default location for SI5.5 local Projects is: C:\Users\*username\Documents\D-Tools SI5 Projects
  2. Open the SIX Client and convert the project using the Import Project feature.
  3. Check In the SI5.5 Project.
  4. Repeat for remaining Projects that you want to convert to the SIX format.

Importing SI5 Custom Reports

 

Click here for information on importing SI5 Custom Reports.

Known Issues

If you did not customize the subreports for your custom reports in SI5, you will likely need to follow the instructions here on how to correct your reports once imported into SIX.

You must to post a comment.
Last modified
08:44, 1 Aug 2014

Tags

This page has no custom tags.

Classifications

This page has no classifications.