Sage 100

 View Only

  • 1.  Moving Payroll to SQL from Providex!

    Posted 07-28-2021 10:35

    We have a Sage 100 v2017 SQL client that is ready to upgrade to v2021. That part of the upgrade will be simple as they core and distribution.

    The challenge is they have a separate Sage 100 ProvideX install on v2017. Long story, but they do. 
    We have finally got management to put them on one install with one maintenance/ subscription.

    I am interested in hearing if anyone has any recommendations or thoughts on putting everything together.

    We typically do a test upgrade to v2021 for payroll to setup all the new tax rules, profiles, and payroll training. 
    We were thinking of doing a test install of Providex to v2021 for the payroll only for this part.
    Next do the SQL upgrade to v2021 and then somehow combine the two install.

    The tricky part would be the migration of the MAS_System folder. My first assumption is to migrate  the MAS_System from the SQL current install and the migration/ upgrade the Payroll install without doing the system files. This of course would mean, re-entering tax profiles, etc.
    But this sounds too simple.


    My concern is the encryption key that is in the company maintenance these days. We have hit a few errors in Sage lately when we do not migrate the system folder. On a different note, I miss the days, when you could just copy and paste a company folder into a new install.

    Should we upgrade payroll to Providex v2021 and then migrate to v2021 SQL from there (without system files) or migrate from v2017 (without system) and reenter tax profiles.

     

    Does anyone have any concerns about payroll being in SQL.(ie Payrate in SQL).  This would be our first Payroll in SQL

    ------------------------------
    Walter Markle
    Warren Averett Technology Group
    ------------------------------


  • 2.  RE: Moving Payroll to SQL from Providex!

    Posted 07-28-2021 10:51
    Open a Sage case / talk with Elliott P.  He helped me with a similar system merge project a few years ago and should be able to talk about whether the new-ish encryption key will be a problem for you. 

    (Our customer was sold Premium before PR 2.0 and they kept a Providex system as just PR for a couple years... then we had to merge it back in as history during a later upgrade).
    Basically, this is what we did:
    • Upgrade 2016 Premium to 2018 Premium, then copy the MAS_WPR data from v2017 into the upgraded v2018 folder (after running pre-migration…) and then doing company conversion on WPR to bring it into SQL.
    Obviously there was a lot of work to get that done (eg. making sure the data dictionary was the same...).  You lose system data in the Providex system, and UserKey will be mismatched in your Providex company being brought in... but you can script fix that in SQL if really important.

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



  • 3.  RE: Moving Payroll to SQL from Providex!

    Posted 07-28-2021 11:38
    >>On a different note, I miss the days, when you could just copy and paste a company folder into a new install.

    I'm happy to be corrected on this

    My understanding is that with encryption you can copy/paste the MAS_XXX so long as you FIRST migrated the data. This means to re-convert you can copy the data files only and it will work. I've done this with the entire MAS_XXX folder ( including payroll ) but only after first having migrated the data.

    I believe the problem with encryption arises if you do NOT first migrate the data and you are coming from a version with an encryption key. If, for example, I had data from company PDQ on a prior version and I manually created company PDQ in a new Sage 100 2021 then tried to drop in MAS_PDQ. My understanding is that an encryption issue occurs.

    ------------------------------
    Wayne Schulz - Schulz Consulting - 860-516-8990
    ------------------------------



  • 4.  RE: Moving Payroll to SQL from Providex!

    Posted 07-28-2021 11:53
    That is my understanding.  Company conversion (for a certain version) sets the encryption key, locking those company files to the system files making company folder copies not work after that.

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

    Original Message


  • 5.  RE: Moving Payroll to SQL from Providex!

    Posted 07-28-2021 12:03
    Yes, making it very difficult to bring client data over to work with.

    ------------------------------
    Beth Bowers
    Mom to Samson, Peanut, ChiChi, Canton, Cagney and Daisy (NO Oxford comma - shriek!)
    Tennessee Software Solutions
    269-445-1625
    ------------------------------

    Original Message


Related Content