So you’ve gotten a bright shiny new server that is a definite upgrade to your previous one but now comes the task of moving over applications from the old one to the new one and this includes Sage 300 ERP.

For this week’s blog post, we will take a look at how to move Sage 300 ERP to a new server.

Before you start to move Sage 300 ERP to a new server make sure you dump the database from the existing server using the Database Dump tool. We have a video that shows you how to perform a Database Dump.

If you are moving Sage 300 ERP to a Microsoft SQL database server, here are the steps to follow.

1. Install Sage 300 ERP on the new server
2. Copy folders and files from the Shared Data Directory from the original server to the new server
3. Recreate the ODBC connections to the Sage 300 ERP databases located on the Microsoft SQL Server. 
4. Recreate the database ID's using Sage 300 ERP Database
5. Use Database Load to load the respective databases

When all of this is done, install the latest product update for your version of Sage 300 ERP.

Other tips to consider:

1. Install the SQL Server that is compatible with Sage 300 ERP along with SQL management studio. Compatible versions include SQL Server 2008, 2012, and 2014.
2. Create the SQL databases (system and company) in SQL Management Studio

1. Create the Sage ERP databases in Database Setup

1. Select server name to point to the SQL databases
2. It will create a DSN with the server name with 32 at the end
3. Confirm the DSN is 32-bit
4. Configure the DSN and select SQL authentication 

If your new server is a Pervasive Database Server then you want to follow these steps:

1. Install Sage 300 ERP on the new server.
2. Copy folders and files from the Shared Data Directory from the original server to the new server.
3. Install:

• Pervasive Server if you are relocating the Pervasive Server to the new server.

• Recreate the database containers on the new Pervasive server with the identical database names as the ones used on the original Pervasive database server.

• Pervasive Client if you want Pervasive Server to remain on a separate dedicated server.
• Pervasive Workgroup if you are using Pervasive Workgroup.

• Recreate the database ID's using Sage 300 ERP Database.
• If you are installing Pervasive Server on the new server, load the database dump into the new Pervasive server using the Sage 300 ERP database load feature.

However, Sage 300 ERP will soon no longer support. Stephen Smith offers more details in his blog post.

General tips regardless of server

You will want to do some test logging to make sure things work. Once you’ve confirmed everything is working properly then schedule to switch over to the new server.

If you have workstations that use workstation setup then configure the DSN to change the SQL server login.

For the latest support news and updates...
Follow us on...
 

If you need more information, consult the Sage 300 ERP Installation and Administration Guide.

Have your own tips to move Sage 300 ERP to a new server? Let us know in the comments.