Sage 100

Anybody done a mas90 to mas 200/erp 100 sql conversion from 4.3 to 4.5? How much extra time, if any, do you need to add due to the database change?

I think @AlnoorCassim

@MarkChinsky we are trying to close and upgrade from 4.1 to 4.5 that will also include a move to SQL. We are proposing two sub projects; one to 4.5 providex, and a second to SQL. We gave a hard quote for the first project and a soft estimate for the second. We will do a dry run internally of the providex to SQL conversion before we give a hard quote. The client has given a verbal commitment but nothing is for real until we get the signed quote and deposit.

It all depends on how big the DB is. We just did a 20 user MAS200 4.05 and it was cake. but the DB was all very manageable size (update. The key is to upgrade to 4.50 pvx and then to 4.50 sql. The other area would be custom reports, they take a liitle more time.,,( so far it is anpther 8 hours for the SQL side. but I am guessing 16 total)

There are too many variables and the best thing to do is a test upgrade to truly find out what you are up against. The size and age of the pvx data is biggest factor and it has a bearing on conversion time and to some extent running into data corruption issues which affects the pvx to SQL conversion. But there isn't a good way to project all that w/o doing an onsite or in-house test upgrade. Having said that, if the size of pvx data to begin with is manageable, then it can be smooth sailing like Jim's example. For custom reports and modified forms, it varies. You can convert all RPTs from 4.40 and most from 4.30 (some Inventory reports need to be manually recreated) to 4.50 SQL via the Mascrcw.exe utility (but use the specific steps mentioned in the Summit SQL powerpoint on this topic - attached). Probably you can convert most of 4.20 and 4.10 as well. But if your starting point is 4.50 pvx, then the RPTs either need to be manually converted within Crystal (manually remove the ""4.50"" in Keywords then Mascrcw.exe) OR recreated altogether. If you're coming from 4.0x or 3.x then they have to be recreated.

Ok thanks. So if a person has a small database and no custom reports its pretty much automatic?

Categorically yes it's straightforward. I would still build in some extra pricing however.

I did a 4.3 EES customer to 4.5 SQL and it went pretty smoothly. They had about 8 years of data, and we did end up doing a test upgrade (they were also going to a new hosted server). The data conversion did seem to take longer than usual, but didn't run into any major issues. Overall the process did not seem anymore difficult than a regular upgrade.