Sage 100

​​I am working on a test migration and upgrade of Sage Premium 2017 to Sage 2020 Premium from an on-premise server to a new hosted server. Because the hosted server cannot see the Sage 2017 SQL server, I am unable to select the "Source" SQL instance to migrate the system and company data from. I've performed all of the steps in KB 42996 (using the "merge" method for the MAS_SYSTEM" database without any errors) up to running the Parallel Migration Utility, but I am not able to use finish with this step in order to pull in custom reports, panels, etc. Carmen Cruz provided a lot of great Premium install/upgrade information some time ago, which I saved, but I don't see anything that helps me work around this part. Sage was not able to help either...they wanted me to work with IT to create a trusted connection between the two domains. I'm hoping there's an easier way. Any tips would be appreciated - I would rather not piece in some of this stuff if I don't have to. Thanks in advance!

------------------------------
Amber Prayfrock, Blytheco
------------------------------

I'd install 2017 Premium on the destination system (or temp hosted server) using a temp SQL instance, then swap in the MAS90 folder and 2017 databases... get that running (SQL permissions, paths... like you would for an unrecoverable server issue, building a new machine from backups), then do the 2020 migration from there.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Thanks, Kevin.  I can try that next.

------------------------------
Amber Prayfrock, Blytheco
------------------------------

Original Message:
Sent: 08-31-2020 16:57
From: Kevin Moyes
Subject: Unable to migrate Premium to hosted server - no "source" SQL connection

I'd install 2017 Premium on the destination system (or temp hosted server) using a temp SQL instance, then swap in the MAS90 folder and 2017 databases... get that running (SQL permissions, paths... like you would for an unrecoverable server issue, building a new machine from backups), then do the 2020 migration from there.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Of course, it would save a lot of effort for you if IT could spin up a VM of the source 2017 system on the hosted network, but that makes more work for someone else...

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 08-31-2020 17:05
From: Amber Prayfrock
Subject: Unable to migrate Premium to hosted server - no "source" SQL connection

Thanks, Kevin.  I can try that next.

------------------------------
Amber Prayfrock, Blytheco
------------------------------


Original Message:
Sent: 08-31-2020 16:57
From: Kevin Moyes
Subject: Unable to migrate Premium to hosted server - no "source" SQL connection

I'd install 2017 Premium on the destination system (or temp hosted server) using a temp SQL instance, then swap in the MAS90 folder and 2017 databases... get that running (SQL permissions, paths... like you would for an unrecoverable server issue, building a new machine from backups), then do the 2020 migration from there.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON

Alternatively, you could backup and zip the 2017 MAS_xxx DBs, MAS_System DB, the whole \Mas90 folder and bring it to your side and do the test migration and conversion to 2020 there. Once done then copy the same stuff, now all converted to 2020, to the hosted system where in the 2020 VM you restore over the existing DBs, replace existing \mas90, and finally run the Premium SQL Settings utility. Now having said all that, umm it's prolly too much work so never mind  :-|  Sorry do what Kevin said about suggesting IT to spin up a VM of the source 2017 system on the hosted network which is visible to the existing VM running the 2020 install and you can tell them hey it's just temporary VM (in case they bring up the SQL on prem vs hosted license issue).

------------------------------
Alnoor Cassim

Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
------------------------------

I'm almost finished with the Sage 2017.2 install and then will test that I can see and access everything before installing Sage 2020 again. I should've just done it this way to begin with...I was just hoping I could make it work without having to install the matching version first. Since I do premiums so infrequently, I forget to ask for certain things as part of the scope so I will just work with my two SQL instances on the same server. Thanks, Kevin and Alnoor!

------------------------------
Amber Prayfrock, Blytheco
------------------------------

Original Message:
Sent: 08-31-2020 19:19
From: Alnoor Cassim
Subject: Unable to migrate Premium to hosted server - no "source" SQL connection

Alternatively, you could backup and zip the 2017 MAS_xxx DBs, MAS_System DB, the whole \Mas90 folder and bring it to your side and do the test migration and conversion to 2020 there. Once done then copy the same stuff, now all converted to 2020, to the hosted system where in the 2020 VM you restore over the existing DBs, replace existing \mas90, and finally run the Premium SQL Settings utility. Now having said all that, umm it's prolly too much work so never mind  :-|  Sorry do what Kevin said about suggesting IT to spin up a VM of the source 2017 system on the hosted network which is visible to the existing VM running the 2020 install and you can tell them hey it's just temporary VM (in case they bring up the SQL on prem vs hosted license issue).

------------------------------
Alnoor Cassim

Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
------------------------------