For the database you should be able to simply backup the database, restore it on the new instance and then run the Sage 500 Sync utility which will sync the users and passwords in the new SQL Instance as well register the license in the new instance. The Crystal Reports are stored by default in each users local folder but most implementations we do and have seen typically get a shared file path configured so everyone is using these files from one path. If that is the case you should all stay intact. You just need to point your current client to the new Sage 500 instance which you can do with the Sage 500 Client Tool found on each workstation.

You would have to migrate your SQL Agent jobs but this can be scripted as well. 

A quick touch point with your Sage Partner would make this simple and clean. 

Joe Noll
RKL eSolutions, LLC

Thanks for the help... I was able to simply backup DB and restore at the new VM... However, since moving and trying to access our data it seems I need to reactivate the modules.



Because I'm testing, I do not want to unregister our current installation... will setting the license type to TEST give us few days/weeks to test? or would you happen to know how can I test the install using our data until we cutoff?

Just as an example, what I do here is the following when moving databases around to other servers.

1) Backup database to move.

2) Restore database to new server.

3) Run the DB Sync utility.  This may add additional SQL users to the server, so if user management is important on the SQL server, note any added users for possible removal later (I can usually go by SQL Server user create date in my testing environments).

4) License the database.

5) In general, in my environments, I do not bother with SQL Server Agent jobs, but you will likely not have that luxury.  This is perhaps another area where a partner chat may be to your benefit.

--------------------------------------------

As Joe mentioned, somewhere along the path you will need to do a DB synchronization using the Sage DB Utilities to bring the users and other things in alignment for the new SQL server instance.  For our internal processing, a synchronization must be done before a licensing request.

-------------------------------------------

I don't believe a previous installation will be unregistered.  If a limit was encountered, I believe a new over the limit registration would be rejected instead.  While I am not really up-to-date on registration processes, I believe you should copy all but the License Type box off of the original server's six controls shown in your post.  For license type, use "test" like you have highlighted now.  If I remember, then this will request a new "test server" license from the Sage license system using the Automatic Internet Registration button.  A test license is very similar to a production license with a few exceptions like 1099 processing where data will be intentionally disabled at some points.  Hopefully, you would then get a registration successful message.

To do this, you would likely need a current support agreement with Sage.  Included in all the cryptic registration message is information tying the specific server information to the customer information and many other things.

Also as mentioned, it might be a good idea to get some advice, tips and tricks from a quality Sage 500 ERP partner.  I am sure he could recommend one if you twisted his arm   There are several who often monitor the Sage City site and as a Sage employee it would be a conflict for me to recommend any particular one of out of the fine pool of partners.