1) Sage 300 - you can use an SQL backup and restore / However the Sage 300 database MUST be the same name otherwise you will get a Sage error - the database name is in every table, so must be the same.

2) Sage CRM - again you can use the SQL backup and restore / However the versions MUST be at the same level as any upgrades can add additional fields, tables etc.

I have attempted to do the restore and the database has the same name.  Are there any other restrictions like the database owner must be the same or anything else?  I have used a test company with a simple backup procedure and also the CRM database that uses the FULL backup method.  When I do the restore I select device and point to the backup file(s) that I have copied from the backup on the old server.  I add the back up device and point to the backup file.  When I attempt to do the restore I receive a restore of database failed.  When I select the details I see a message that the backup is of a different database.  The backup is from SQL 2008R2 and the new server is SQL 2017.  Any ideas?

If you do not knowhow  to use SQL, then I can not really teach you on the forum: (You need to find somebody in the client IT department who knows SQL, or in your own company).

1) the new SQL does not like to do a restore unless you have done a backup first - I found this out the hard way after spending a long time trying to restore.

2) there is a boxes that needs to be ticked to change the names over

3) you can also change the names in the section where it has the file & log

4) the database name is the S300 name that you allocate in the S300 database maintenance screen - that must be the same.

I solved this.  All I had to do was delete the database in the new SQL server and let it create everything when I did the restore.  It was very simple, but it would not work if I created the empty database first.

FYI - It also works even if you have already defined the tables - you just need to know your SQL restore settings that need to be changed at restore time.

You may have the occasion where you want to bring the databases over again as this one was just a test - you want to just do a restore into those tables that are already there.  You can do this by changing the setting in the SQL restore option.

You can also use SQL's detach/attach functionality. This saves time as SQL does not need to create a backup file. Downside is you need to find the physical database and log files and move them.

Advantages of using backup option are all files are grouped in your saved location, and you can use SQL compression to reduce the DB size.