Sage 100

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444


Original Message:
Sent: 03-22-2024 17:47
From: Doug Higgs
Subject: Upgrade from version 3.2 including Payroll

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

We do have a KB on migrating from older ( 3.x ) to newer Sage 100. 

https://docs.google.com/document/d/1fxDePNFgYLMokY0lSL9Et8w4AHf1hhxGEcpkJ1Df8Gg/edit#heading=h.gb8b4vkpvdmv

We really do need a technical review on these KB articles as I try to document what I've done. However, there are almost always additional approaches or information to be added.

I did a 3. x to 2023 with payroll over this summer, and my notes are: 

1. Get to 3.71
2. Upgrade to 4.5 PU8 ( note that the "stop" may vary depending on whether you have payroll or not. I usually don't see old versions of Sage 100 at v3.x that also have payroll), and if this customer hadn't had payroll, I would have gone to 2017.
3. Upgrade to 2023.x

TLDR: We need helpers to review KB articles and add/correct things. Please reach out to me and I'll let you know when the next meeting of the KB Club is.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT
------------------------------


Original Message:
Sent: 03-22-2024 19:05
From: Kevin Moyes
Subject: Upgrade from version 3.2 including Payroll

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444


Original Message:
Sent: 03-22-2024 17:47
From: Doug Higgs
Subject: Upgrade from version 3.2 including Payroll

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

I rarely go to 4.5.8 and most often go to v2017 (especially since I prefer to work with the more recent version), unless for example the client is running 4.5.x in which case I'll just slap in PU8.  Or in some instances I'll bring them to .8 if there's something about their enhancements that warrants it.  I actually don't recall ever taking Payroll into consideration in these scenarios.  Did I miss a memo?  :)

We do have a KB on migrating from older ( 3.x ) to newer Sage 100. 

https://docs.google.com/document/d/1fxDePNFgYLMokY0lSL9Et8w4AHf1hhxGEcpkJ1Df8Gg/edit#heading=h.gb8b4vkpvdmv

We really do need a technical review on these KB articles as I try to document what I've done. However, there are almost always additional approaches or information to be added.

I did a 3. x to 2023 with payroll over this summer, and my notes are: 

1. Get to 3.71
2. Upgrade to 4.5 PU8 ( note that the "stop" may vary depending on whether you have payroll or not. I usually don't see old versions of Sage 100 at v3.x that also have payroll), and if this customer hadn't had payroll, I would have gone to 2017.
3. Upgrade to 2023.x

TLDR: We need helpers to review KB articles and add/correct things. Please reach out to me and I'll let you know when the next meeting of the KB Club is.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 03-22-2024 19:05
From: Kevin Moyes
Subject: Upgrade from version 3.2 including Payroll

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444


Original Message:
Sent: 03-22-2024 17:47
From: Doug Higgs
Subject: Upgrade from version 3.2 including Payroll

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

The only reason I stopped at 4.5 PU8 was payroll. Otherwise, I would have gone 3.x to 3.71 to 20I7 to 2023. I don't know if going 3.71 to 4.5 PU8 was beneficial but because I rarely see Payroll UG from 3.x that was my "game time decision". I remembered having this note from a conversation with Sage and I figured that since I also had four companies with payroll that I was upgrading that I'd rather play it safe.

It's possible that 3.71 to 2017 to 2023 with payroll would have worked just as well

I have these notes from Sage's John Nichols: 

When Might Sage 100 4.5 PU8 Be Required as an Interim Stop During Upgrades From Earlier Versions 

Updated Jul 20, 2023 by Wayne Schulz

Per discussion with Sage John Nichols:

• The reasoning behind the decision to require users to be at 4.50 PU8 to convert to 2018 (6.0) is below:

• All modules except P/R, J/C, W/O, and MRP would have previously been converted to framework levels, and the bulk of the extensive conversions would have been completed.

• The conversion checks the version, not installed modules, and we could not change this requirement based on which modules (P/R, J/C) were or were not installed. 

• 4.50 PU8 contained the ACA (Affordable Care Act) and IRD compliance schema and code, which minimized the conversion to 2018 Payroll.

• The team had the highest confidence in the level conversion from 4.50.8 to 2018.

Note: You could also go to 2017, but that may be the highest level to take a 3.x directly.

I rarely go to 4.5.8 and most often go to v2017 (especially since I prefer to work with the more recent version), unless for example the client is running 4.5.x in which case I'll just slap in PU8.  Or in some instances I'll bring them to .8 if there's something about their enhancements that warrants it.  I actually don't recall ever taking Payroll into consideration in these scenarios.  Did I miss a memo?  :)

We do have a KB on migrating from older ( 3.x ) to newer Sage 100. 

https://docs.google.com/document/d/1fxDePNFgYLMokY0lSL9Et8w4AHf1hhxGEcpkJ1Df8Gg/edit#heading=h.gb8b4vkpvdmv

We really do need a technical review on these KB articles as I try to document what I've done. However, there are almost always additional approaches or information to be added.

I did a 3. x to 2023 with payroll over this summer, and my notes are: 

1. Get to 3.71
2. Upgrade to 4.5 PU8 ( note that the "stop" may vary depending on whether you have payroll or not. I usually don't see old versions of Sage 100 at v3.x that also have payroll), and if this customer hadn't had payroll, I would have gone to 2017.
3. Upgrade to 2023.x

TLDR: We need helpers to review KB articles and add/correct things. Please reach out to me and I'll let you know when the next meeting of the KB Club is.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 03-22-2024 19:05
From: Kevin Moyes
Subject: Upgrade from version 3.2 including Payroll

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444

The only reason I stopped at 4.5 PU8 was payroll. Otherwise, I would have gone 3.x to 3.71 to 20I7 to 2023. I don't know if going 3.71 to 4.5 PU8 was beneficial but because I rarely see Payroll UG from 3.x that was my "game time decision". I remembered having this note from a conversation with Sage and I figured that since I also had four companies with payroll that I was upgrading that I'd rather play it safe.

It's possible that 3.71 to 2017 to 2023 with payroll would have worked just as well

I have these notes from Sage's John Nichols: 

When Might Sage 100 4.5 PU8 Be Required as an Interim Stop During Upgrades From Earlier Versions 

Updated Jul 20, 2023 by Wayne Schulz

Per discussion with Sage John Nichols:

• The reasoning behind the decision to require users to be at 4.50 PU8 to convert to 2018 (6.0) is below:

• All modules except P/R, J/C, W/O, and MRP would have previously been converted to framework levels, and the bulk of the extensive conversions would have been completed.

• The conversion checks the version, not installed modules, and we could not change this requirement based on which modules (P/R, J/C) were or were not installed. 

• 4.50 PU8 contained the ACA (Affordable Care Act) and IRD compliance schema and code, which minimized the conversion to 2018 Payroll.

• The team had the highest confidence in the level conversion from 4.50.8 to 2018.

Note: You could also go to 2017, but that may be the highest level to take a 3.x directly.

I rarely go to 4.5.8 and most often go to v2017 (especially since I prefer to work with the more recent version), unless for example the client is running 4.5.x in which case I'll just slap in PU8.  Or in some instances I'll bring them to .8 if there's something about their enhancements that warrants it.  I actually don't recall ever taking Payroll into consideration in these scenarios.  Did I miss a memo?  :)

We do have a KB on migrating from older ( 3.x ) to newer Sage 100. 

https://docs.google.com/document/d/1fxDePNFgYLMokY0lSL9Et8w4AHf1hhxGEcpkJ1Df8Gg/edit#heading=h.gb8b4vkpvdmv

We really do need a technical review on these KB articles as I try to document what I've done. However, there are almost always additional approaches or information to be added.

I did a 3. x to 2023 with payroll over this summer, and my notes are: 

1. Get to 3.71
2. Upgrade to 4.5 PU8 ( note that the "stop" may vary depending on whether you have payroll or not. I usually don't see old versions of Sage 100 at v3.x that also have payroll), and if this customer hadn't had payroll, I would have gone to 2017.
3. Upgrade to 2023.x

TLDR: We need helpers to review KB articles and add/correct things. Please reach out to me and I'll let you know when the next meeting of the KB Club is.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 03-22-2024 19:05
From: Kevin Moyes
Subject: Upgrade from version 3.2 including Payroll

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444


Original Message:
Sent: 03-22-2024 17:47
From: Doug Higgs
Subject: Upgrade from version 3.2 including Payroll

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

David,

The one thing I don't see discussed here is Inventory. Way back in the day I seem to recall that anyone who was on a pre-3.51 version and wanted to get to 3.71 or above, the important question was whether they had Inventory. Wasn't there a major rewrite of the Inventory module for 3.51?

I may be wrong, and you may have the exact correct steps. Hard to believe someone is still running on anything older than 3.71 in this day and age.

Good luck.

The only reason I stopped at 4.5 PU8 was payroll. Otherwise, I would have gone 3.x to 3.71 to 20I7 to 2023. I don't know if going 3.71 to 4.5 PU8 was beneficial but because I rarely see Payroll UG from 3.x that was my "game time decision". I remembered having this note from a conversation with Sage and I figured that since I also had four companies with payroll that I was upgrading that I'd rather play it safe.

It's possible that 3.71 to 2017 to 2023 with payroll would have worked just as well

I have these notes from Sage's John Nichols: 

When Might Sage 100 4.5 PU8 Be Required as an Interim Stop During Upgrades From Earlier Versions 

Updated Jul 20, 2023 by Wayne Schulz

Per discussion with Sage John Nichols:

• The reasoning behind the decision to require users to be at 4.50 PU8 to convert to 2018 (6.0) is below:

• All modules except P/R, J/C, W/O, and MRP would have previously been converted to framework levels, and the bulk of the extensive conversions would have been completed.

• The conversion checks the version, not installed modules, and we could not change this requirement based on which modules (P/R, J/C) were or were not installed. 

• 4.50 PU8 contained the ACA (Affordable Care Act) and IRD compliance schema and code, which minimized the conversion to 2018 Payroll.

• The team had the highest confidence in the level conversion from 4.50.8 to 2018.

Note: You could also go to 2017, but that may be the highest level to take a 3.x directly.

I rarely go to 4.5.8 and most often go to v2017 (especially since I prefer to work with the more recent version), unless for example the client is running 4.5.x in which case I'll just slap in PU8.  Or in some instances I'll bring them to .8 if there's something about their enhancements that warrants it.  I actually don't recall ever taking Payroll into consideration in these scenarios.  Did I miss a memo?  :)

We do have a KB on migrating from older ( 3.x ) to newer Sage 100. 

https://docs.google.com/document/d/1fxDePNFgYLMokY0lSL9Et8w4AHf1hhxGEcpkJ1Df8Gg/edit#heading=h.gb8b4vkpvdmv

We really do need a technical review on these KB articles as I try to document what I've done. However, there are almost always additional approaches or information to be added.

I did a 3. x to 2023 with payroll over this summer, and my notes are: 

1. Get to 3.71
2. Upgrade to 4.5 PU8 ( note that the "stop" may vary depending on whether you have payroll or not. I usually don't see old versions of Sage 100 at v3.x that also have payroll), and if this customer hadn't had payroll, I would have gone to 2017.
3. Upgrade to 2023.x

TLDR: We need helpers to review KB articles and add/correct things. Please reach out to me and I'll let you know when the next meeting of the KB Club is.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 03-22-2024 19:05
From: Kevin Moyes
Subject: Upgrade from version 3.2 including Payroll

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444

David,

The one thing I don't see discussed here is Inventory. Way back in the day I seem to recall that anyone who was on a pre-3.51 version and wanted to get to 3.71 or above, the important question was whether they had Inventory. Wasn't there a major rewrite of the Inventory module for 3.51?

I may be wrong, and you may have the exact correct steps. Hard to believe someone is still running on anything older than 3.71 in this day and age.

Good luck.

The only reason I stopped at 4.5 PU8 was payroll. Otherwise, I would have gone 3.x to 3.71 to 20I7 to 2023. I don't know if going 3.71 to 4.5 PU8 was beneficial but because I rarely see Payroll UG from 3.x that was my "game time decision". I remembered having this note from a conversation with Sage and I figured that since I also had four companies with payroll that I was upgrading that I'd rather play it safe.

It's possible that 3.71 to 2017 to 2023 with payroll would have worked just as well

I have these notes from Sage's John Nichols: 

When Might Sage 100 4.5 PU8 Be Required as an Interim Stop During Upgrades From Earlier Versions 

Updated Jul 20, 2023 by Wayne Schulz

Per discussion with Sage John Nichols:

• The reasoning behind the decision to require users to be at 4.50 PU8 to convert to 2018 (6.0) is below:

• All modules except P/R, J/C, W/O, and MRP would have previously been converted to framework levels, and the bulk of the extensive conversions would have been completed.

• The conversion checks the version, not installed modules, and we could not change this requirement based on which modules (P/R, J/C) were or were not installed. 

• 4.50 PU8 contained the ACA (Affordable Care Act) and IRD compliance schema and code, which minimized the conversion to 2018 Payroll.

• The team had the highest confidence in the level conversion from 4.50.8 to 2018.

Note: You could also go to 2017, but that may be the highest level to take a 3.x directly.

I rarely go to 4.5.8 and most often go to v2017 (especially since I prefer to work with the more recent version), unless for example the client is running 4.5.x in which case I'll just slap in PU8.  Or in some instances I'll bring them to .8 if there's something about their enhancements that warrants it.  I actually don't recall ever taking Payroll into consideration in these scenarios.  Did I miss a memo?  :)

We do have a KB on migrating from older ( 3.x ) to newer Sage 100. 

https://docs.google.com/document/d/1fxDePNFgYLMokY0lSL9Et8w4AHf1hhxGEcpkJ1Df8Gg/edit#heading=h.gb8b4vkpvdmv

We really do need a technical review on these KB articles as I try to document what I've done. However, there are almost always additional approaches or information to be added.

I did a 3. x to 2023 with payroll over this summer, and my notes are: 

1. Get to 3.71
2. Upgrade to 4.5 PU8 ( note that the "stop" may vary depending on whether you have payroll or not. I usually don't see old versions of Sage 100 at v3.x that also have payroll), and if this customer hadn't had payroll, I would have gone to 2017.
3. Upgrade to 2023.x

TLDR: We need helpers to review KB articles and add/correct things. Please reach out to me and I'll let you know when the next meeting of the KB Club is.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 03-22-2024 19:05
From: Kevin Moyes
Subject: Upgrade from version 3.2 including Payroll

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444


Original Message:
Sent: 03-22-2024 17:47
From: Doug Higgs
Subject: Upgrade from version 3.2 including Payroll

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

I see about one or two odd upgrades a year. What's starting to happen is that some or many of the companies on older versions are simultaneously retiring, so it's frequently a request for a band-aid rather than a complete upgrade.

However, I did have one upgrade with payroll on 3.x and they manually were computing the taxes. In many cases, these are end-users for whom the CPA may be pseudo-supporting and advising them to hold off on spending money, etc.

David,

The one thing I don't see discussed here is Inventory. Way back in the day I seem to recall that anyone who was on a pre-3.51 version and wanted to get to 3.71 or above, the important question was whether they had Inventory. Wasn't there a major rewrite of the Inventory module for 3.51?

I may be wrong, and you may have the exact correct steps. Hard to believe someone is still running on anything older than 3.71 in this day and age.

Good luck.

The only reason I stopped at 4.5 PU8 was payroll. Otherwise, I would have gone 3.x to 3.71 to 20I7 to 2023. I don't know if going 3.71 to 4.5 PU8 was beneficial but because I rarely see Payroll UG from 3.x that was my "game time decision". I remembered having this note from a conversation with Sage and I figured that since I also had four companies with payroll that I was upgrading that I'd rather play it safe.

It's possible that 3.71 to 2017 to 2023 with payroll would have worked just as well

I have these notes from Sage's John Nichols: 

When Might Sage 100 4.5 PU8 Be Required as an Interim Stop During Upgrades From Earlier Versions 

Updated Jul 20, 2023 by Wayne Schulz

Per discussion with Sage John Nichols:

• The reasoning behind the decision to require users to be at 4.50 PU8 to convert to 2018 (6.0) is below:

• All modules except P/R, J/C, W/O, and MRP would have previously been converted to framework levels, and the bulk of the extensive conversions would have been completed.

• The conversion checks the version, not installed modules, and we could not change this requirement based on which modules (P/R, J/C) were or were not installed. 

• 4.50 PU8 contained the ACA (Affordable Care Act) and IRD compliance schema and code, which minimized the conversion to 2018 Payroll.

• The team had the highest confidence in the level conversion from 4.50.8 to 2018.

Note: You could also go to 2017, but that may be the highest level to take a 3.x directly.

I rarely go to 4.5.8 and most often go to v2017 (especially since I prefer to work with the more recent version), unless for example the client is running 4.5.x in which case I'll just slap in PU8.  Or in some instances I'll bring them to .8 if there's something about their enhancements that warrants it.  I actually don't recall ever taking Payroll into consideration in these scenarios.  Did I miss a memo?  :)

We do have a KB on migrating from older ( 3.x ) to newer Sage 100. 

https://docs.google.com/document/d/1fxDePNFgYLMokY0lSL9Et8w4AHf1hhxGEcpkJ1Df8Gg/edit#heading=h.gb8b4vkpvdmv

We really do need a technical review on these KB articles as I try to document what I've done. However, there are almost always additional approaches or information to be added.

I did a 3. x to 2023 with payroll over this summer, and my notes are: 

1. Get to 3.71
2. Upgrade to 4.5 PU8 ( note that the "stop" may vary depending on whether you have payroll or not. I usually don't see old versions of Sage 100 at v3.x that also have payroll), and if this customer hadn't had payroll, I would have gone to 2017.
3. Upgrade to 2023.x

TLDR: We need helpers to review KB articles and add/correct things. Please reach out to me and I'll let you know when the next meeting of the KB Club is.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 03-22-2024 19:05
From: Kevin Moyes
Subject: Upgrade from version 3.2 including Payroll

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444


Original Message:
Sent: 03-22-2024 17:47
From: Doug Higgs
Subject: Upgrade from version 3.2 including Payroll

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

Small CPA firms seem to have a vested interest when advising clients NOT to spend money on anything other than on the CPA practice consulting.  Somewhat of a racket, IMHO.  

I see about one or two odd upgrades a year. What's starting to happen is that some or many of the companies on older versions are simultaneously retiring, so it's frequently a request for a band-aid rather than a complete upgrade.

However, I did have one upgrade with payroll on 3.x and they manually were computing the taxes. In many cases, these are end-users for whom the CPA may be pseudo-supporting and advising them to hold off on spending money, etc.

David,

The one thing I don't see discussed here is Inventory. Way back in the day I seem to recall that anyone who was on a pre-3.51 version and wanted to get to 3.71 or above, the important question was whether they had Inventory. Wasn't there a major rewrite of the Inventory module for 3.51?

I may be wrong, and you may have the exact correct steps. Hard to believe someone is still running on anything older than 3.71 in this day and age.

Good luck.

The only reason I stopped at 4.5 PU8 was payroll. Otherwise, I would have gone 3.x to 3.71 to 20I7 to 2023. I don't know if going 3.71 to 4.5 PU8 was beneficial but because I rarely see Payroll UG from 3.x that was my "game time decision". I remembered having this note from a conversation with Sage and I figured that since I also had four companies with payroll that I was upgrading that I'd rather play it safe.

It's possible that 3.71 to 2017 to 2023 with payroll would have worked just as well

I have these notes from Sage's John Nichols: 

When Might Sage 100 4.5 PU8 Be Required as an Interim Stop During Upgrades From Earlier Versions 

Updated Jul 20, 2023 by Wayne Schulz

Per discussion with Sage John Nichols:

• The reasoning behind the decision to require users to be at 4.50 PU8 to convert to 2018 (6.0) is below:

• All modules except P/R, J/C, W/O, and MRP would have previously been converted to framework levels, and the bulk of the extensive conversions would have been completed.

• The conversion checks the version, not installed modules, and we could not change this requirement based on which modules (P/R, J/C) were or were not installed. 

• 4.50 PU8 contained the ACA (Affordable Care Act) and IRD compliance schema and code, which minimized the conversion to 2018 Payroll.

• The team had the highest confidence in the level conversion from 4.50.8 to 2018.

Note: You could also go to 2017, but that may be the highest level to take a 3.x directly.

I rarely go to 4.5.8 and most often go to v2017 (especially since I prefer to work with the more recent version), unless for example the client is running 4.5.x in which case I'll just slap in PU8.  Or in some instances I'll bring them to .8 if there's something about their enhancements that warrants it.  I actually don't recall ever taking Payroll into consideration in these scenarios.  Did I miss a memo?  :)

We do have a KB on migrating from older ( 3.x ) to newer Sage 100. 

https://docs.google.com/document/d/1fxDePNFgYLMokY0lSL9Et8w4AHf1hhxGEcpkJ1Df8Gg/edit#heading=h.gb8b4vkpvdmv

We really do need a technical review on these KB articles as I try to document what I've done. However, there are almost always additional approaches or information to be added.

I did a 3. x to 2023 with payroll over this summer, and my notes are: 

1. Get to 3.71
2. Upgrade to 4.5 PU8 ( note that the "stop" may vary depending on whether you have payroll or not. I usually don't see old versions of Sage 100 at v3.x that also have payroll), and if this customer hadn't had payroll, I would have gone to 2017.
3. Upgrade to 2023.x

TLDR: We need helpers to review KB articles and add/correct things. Please reach out to me and I'll let you know when the next meeting of the KB Club is.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 03-22-2024 19:05
From: Kevin Moyes
Subject: Upgrade from version 3.2 including Payroll

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444


Original Message:
Sent: 03-22-2024 17:47
From: Doug Higgs
Subject: Upgrade from version 3.2 including Payroll

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles

... or move them to Quickbooks. 

Small CPA firms seem to have a vested interest when advising clients NOT to spend money on anything other than on the CPA practice consulting.  Somewhat of a racket, IMHO.  

I see about one or two odd upgrades a year. What's starting to happen is that some or many of the companies on older versions are simultaneously retiring, so it's frequently a request for a band-aid rather than a complete upgrade.

However, I did have one upgrade with payroll on 3.x and they manually were computing the taxes. In many cases, these are end-users for whom the CPA may be pseudo-supporting and advising them to hold off on spending money, etc.

David,

The one thing I don't see discussed here is Inventory. Way back in the day I seem to recall that anyone who was on a pre-3.51 version and wanted to get to 3.71 or above, the important question was whether they had Inventory. Wasn't there a major rewrite of the Inventory module for 3.51?

I may be wrong, and you may have the exact correct steps. Hard to believe someone is still running on anything older than 3.71 in this day and age.

Good luck.

The only reason I stopped at 4.5 PU8 was payroll. Otherwise, I would have gone 3.x to 3.71 to 20I7 to 2023. I don't know if going 3.71 to 4.5 PU8 was beneficial but because I rarely see Payroll UG from 3.x that was my "game time decision". I remembered having this note from a conversation with Sage and I figured that since I also had four companies with payroll that I was upgrading that I'd rather play it safe.

It's possible that 3.71 to 2017 to 2023 with payroll would have worked just as well

I have these notes from Sage's John Nichols: 

When Might Sage 100 4.5 PU8 Be Required as an Interim Stop During Upgrades From Earlier Versions 

Updated Jul 20, 2023 by Wayne Schulz

Per discussion with Sage John Nichols:

• The reasoning behind the decision to require users to be at 4.50 PU8 to convert to 2018 (6.0) is below:

• All modules except P/R, J/C, W/O, and MRP would have previously been converted to framework levels, and the bulk of the extensive conversions would have been completed.

• The conversion checks the version, not installed modules, and we could not change this requirement based on which modules (P/R, J/C) were or were not installed. 

• 4.50 PU8 contained the ACA (Affordable Care Act) and IRD compliance schema and code, which minimized the conversion to 2018 Payroll.

• The team had the highest confidence in the level conversion from 4.50.8 to 2018.

Note: You could also go to 2017, but that may be the highest level to take a 3.x directly.

I rarely go to 4.5.8 and most often go to v2017 (especially since I prefer to work with the more recent version), unless for example the client is running 4.5.x in which case I'll just slap in PU8.  Or in some instances I'll bring them to .8 if there's something about their enhancements that warrants it.  I actually don't recall ever taking Payroll into consideration in these scenarios.  Did I miss a memo?  :)

We do have a KB on migrating from older ( 3.x ) to newer Sage 100. 

https://docs.google.com/document/d/1fxDePNFgYLMokY0lSL9Et8w4AHf1hhxGEcpkJ1Df8Gg/edit#heading=h.gb8b4vkpvdmv

We really do need a technical review on these KB articles as I try to document what I've done. However, there are almost always additional approaches or information to be added.

I did a 3. x to 2023 with payroll over this summer, and my notes are: 

1. Get to 3.71
2. Upgrade to 4.5 PU8 ( note that the "stop" may vary depending on whether you have payroll or not. I usually don't see old versions of Sage 100 at v3.x that also have payroll), and if this customer hadn't had payroll, I would have gone to 2017.
3. Upgrade to 2023.x

TLDR: We need helpers to review KB articles and add/correct things. Please reach out to me and I'll let you know when the next meeting of the KB Club is.

------------------------------
Wayne Schulz
wayne@s-consult.com
Schulz Consulting
(860) 516-8990
Moodus, CT


Original Message:
Sent: 03-22-2024 19:05
From: Kevin Moyes
Subject: Upgrade from version 3.2 including Payroll

Details / considerations for upgrades from old versions would be an excellent topic for the 90-Minds knowledge base that is being worked on... (by a 90M committee?). 

I remember seeing threads in the past about this kind of project, but searching discussion history is not always easy.

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


Original Message:
Sent: 03-22-2024 19:00
From: Jeff Schwenk
Subject: Upgrade from version 3.2 including Payroll

i am sure this has been commented on before here.  I am at a loss for the search words.  I bet @Wayne Schulz knows the combination....

------------------------------
Jeff Schwenk
Bottomline Software, Inc.
(540) 221-4444


Original Message:
Sent: 03-22-2024 17:47
From: Doug Higgs
Subject: Upgrade from version 3.2 including Payroll

I did a MAS 200 3.74 to several years ago and the upgrade path was: 3.74 -> 3.71 -> 4.40 PVX -> 4.50 for SQL using the SQL migration utility.  Not sure if MAS90 / Standard is the same so I wonder if you need to go to 4.4 first before 4.5.  Of course you can test it to find out.

------------------------------
Doug Higgs
Midwest Commerce Solutions, Inc
(312) 315-0960
Chauffeur, Chef, and Personal Assistant to Sprinkles