Sage 100

Is anyone aware of documentation on migration from Sage100 Advanced to Sage 100 Premium (Providex to SQL Migration). I've scoured that portal site, installation guides, and upgrade guides. and have not found anything yet. still looking though!

I believe that @AlnoorCassim has done a few and @DawnAnastasi

I think @JimWoodhead has done this also.

All you have to do is copy the ProvideX data into the directory and go into company maintenance and convert.

So I install the SQL version, Create my company using the same company code, copy the ProvideX data from my current installation and go to company maintenance and convert? I don't even need to do ""Migrate data?"" sounds simple enough. Do the versions have to match? do the service packs need to match? for example my client is running Sage100 advanced version 4.40.08 and they want to go to SAGE100 premium Version 4.50.04 do I need to upgrade the ProvideX to version 4.50.04 first? Still seems like there should be a document somewhere or maybe I'm making it more difficult that it should be.

What about security, forms/reports, etc? This only converts data, not system files?

exactyly - you might expect a providex to SQL migration document to cover such topics

I think their documentation is lacking.

I believe at one point DSD offered up a utility that did this providex to SQL migration though my memory is that it may have had some restrictions on versions - @JimWoodhead ?

This should be obsolete now that MAS 200 can convert natively from ProvideX to SQL. Although you do have to convert your reports to using the SQL OLEDB connection instead of the SOTAMAS90 connection.

@DavidOverholt as we are quoting a similar upgrade for a client, we have been doing a lot of digging on this. The Sage ERP MAS 90 and 200 Upgradeing and Migrating class offered in SageU covers this upgrade process. Per the manual (Curriculum Version 1.0), the process is the same whether moving to Provi!deX or SQL. Page 1 - ""This course provides information for upgrading and migrating all version of Sage ERP MAS 90 and 200, including Sage ERP MAS 200 SQL."" We will be running a test internally later this month and will report back to the group on findings, experience, gotchas, etc. BTW, we have contacted Aloon and asked him to be our back-up in we run into anything unexpectedly hairy.

Thanks Shawn, We are in the quoting process as well, We passed the SQL class (i think about a year ago). I'll locate the Class materials.

Shawn, Alnoor can be a loon! ;)

Some misc notes: * If you're migrating from a pvx version prior to 4.50 you use the same Parallel Migration wizard. It will ask you if you're coming from SQL or non-SQL * After migrating the conversion in Comp Maint will internally convert data to 4.50 pvx before it converts to 4.50 SQL. For 4.45 you had multiple manual steps. * When installing a product update (e.g. PU4) when asked if you want to scan your data files for corruption it will recognize existing company databases but thrown an exception error when you say Yes (but maybe that's just me) * All the standard forms and reports it installs are the same exact reports installed by 4.50 pvx based on SOTAMAS90. When you print / preview it will map the tables to the SQLOLEDB provider and run against the SQL tables. This mapping is done in memory - the .RPT file isn't touched and is still set for SOTAMAS90. The on-the-fly mapping to SQL OLEDB also occurs with running migrated reports that are using SOTAMAS90 on Custom Reports menu (but if you later modify custom report and need to see data from inside CR designer, then convert it to SQL OLEDB).