Parallel Migration for Selective Modules

I have several clients in the region that need to upgrade from 2017 to 2022 prior to September 2023.  This includes the payroll module.  Unfortunately, Sage did not release the payroll module with tax calculations specific to clients' jurisdiction.  They are working on it.  In the meantime the clients would like to upgrade now to make sure their systems don't go into read only mode.  I have installed 2022 including new payroll and tested (with exception of payroll tax calculation).  My question is if there is any way to perform a selective module parallel migration rather than company wide?  If I perform a parallel migration now (and they go live) and then when the tax tables are developed by Sage and ready for deployment perform another parallel migration the data will be overwritten in 2022.  I suppose I could back up 2022 data prior to second migration, perform the migration to include payroll, and then restore the company data files for non-payroll modules.  Any other ideas?

  • 0

    No.  You need to upgrade the entire Sage 100 Company at the same time.  There is no "urgent need" to be on v2022 prior to October 2023 (for TLS Purposes).  I would not recommend making this overly complicated since not only Payroll would be impacted but the general ledger also.  Not to mention actually "actively using" two version installs of Sage 100 is not supported with your Sage 100 Licensing.  

  • 0 in reply to StefanouM

    I was forced to split a system once (customer was sold Premium before payroll 2.0 was released) and it was a nightmare.  (Yes, we did the split with permission from Sage). 

    In the end, the payroll history was brought in as an archive company code and they started using the new payroll without the history in their Live company code.  Don't even try to merge the data, and delay if you can.  At the time we talked through options, and there was nothing feasible to merge in the payroll data that was running separately (for a couple years).