Skip to content
logo Knowledgebase

Migrating from Sage Line 100 to Sage 200

Created on  | Last modified on 

Summary

Migrating from Sage Line 100 to Sage 200

Description

Sage Line 100: Important Information


We recently became aware of an arithmetic anomaly which, due to age of the software, will impact the ability to process live transactions, such as month end processes, raising sales orders or goods received after 17 September 2021. We are unable to offer a fix that will support the continued use of Sage Line 100.

This article outlines the process required to migrate your data to Sage 200 but please note the following points before proceeding:

  • Sage Line 100 was assigned 'end-of-life' status on 31 March 2014.
  • The Migration Tool referred to in this article can be used on Sage Line 100 versions 7.2 to 7.6.
  • The Migration Tool can only migrate data to Sage 200 version 2010 as an interim version, from where you can then upgrade to the latest version of Sage 200. If you require an enable string for Sage 200 version 2010 and/or version 2011, or older versions of the software, please contact [email protected]. Keys will be issued with three months' validity to authorised Sage 200 partners. If you are Sage 100 user and/or are not an authorised Sage 200 partner, please contact [email protected] for further advice. 
  • Please note we cannot guarantee full data migration where a bespoke Line 100 installation is used which has changed the Sage Line 100 data files.
  • It is not possible to upgrade reports or stationery layouts.
  • This information is provided as a courtesy on an end-of-life product. Sage Technical Support are unable to support these older versions of Sage Line 100 or Sage 200.

Resolution

EXAMPLE MIGRATION

01. You must upgrade Sage Line 100 v7.2 (or v7.6) to Sage 200 version 2010 via the Migration Tool. This applies regardless of whether or not the Bill of Materials module has been used. 

02. As you cannot install different versions of Sage Line 100 or Sage 200 on the same PC or virtual image, you will need to install Sage 200 version 2010 on a separate virtual image or PC. Note however that you may recreate the Line 100 folder structure on your new image/machine to save having to install Sage Line 100 on your Sage 200 version 2010 image. To do this, copy over the SVNDATA folder that holds the REL and RIN files (data files) into the structure e.g. C:\SAGE\SVNDATA.

03. Use the Migration Tool v6.0.57.10 to upgrade from Sage Line 100 v7.2 or above to Sage 200 version 2010. The preparation and help files are available from within the Migration Tool once you have installed it.

04. Once migration to Sage 200 version 2010 is complete, you must then upgrade from Sage 200 2010 to Sage 200 2011 with Service Pack 7. Note you will need version 2011 or later installed on another virtual image or PC. Note that this step is mandatory as migration to version 2013 has only been tested via Sage 200 2011.

05. Upgrade from Sage 200 2011 Service Pack 7 to Sage 200 2013 R2. Again, you will need version 2013 R2 installed on another virtual image or PC.

06. You may then upgrade Sage 200 2013 R2 to the latest version of Sage 200. Again, you will need this new version installed on another virtual image or PC.