Sage 100

 View Only

  • 1.  Payroll on its own installation, need to merge to another installation

    Posted 01-27-2022 16:34
    This is a bit messy!

    Customer is on 2018.10.  they own payroll, but not sure it's currently installed.

    Their accountants have been doing the payroll for customer and have a copy of customer's Sage (Keys, not data) with payroll installed on their own system (yes, we won't even go there).  I believe payroll was processed and a journal entry was sent to Customer to make in their own system.

    Customer has now outsourced payroll.

    Customer wants to upgrade and take payroll with for historical purposes. 

    My Problem:  GL/AP/AR is on 1 install, PR is on another.

    Wondering if you think this will work:  Install/Activate PR on customer's system that has GL/AP/AR, copy the PRxxx folder from accountant's system.  They are going to keep 1 user for access to reports, etc.  I know that any 'links' between GL & PR won't be valid, but I don't think that's a concern.  I'm concerned about whether the 'piecemealed' payroll will migrate correctly to v2021.

    Any other thoughts about how to do this?
    N



    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------


  • 2.  RE: Payroll on its own installation, need to merge to another installation

    Posted 01-27-2022 16:58

    I have a feeling that if you just use a window's copy of the payroll folder into the customer's installation then the encryption keys would cause you problems. I think you need to migrate.

     

    I would:

    ·         On the accountant's install, copy the data to a new different company code (PRB in my example)

    ·         Copy the MAS90 folder from the accountants over to customers server. I would include program folders and system folders, but just the company code(s) you want brought into the customer's install.

    ·         Install PR on the customer's system

    ·         Migrate the "PRB" company into the customer's install from the accountant's install. That will then have the correct company encryption keys.

     

     

     

     

     

    David Overholt

    DWD Technology Group, Inc.

    9921 Dupont Circle Drive West, Suite 300 | Fort Wayne, IN 46825

    260.423.2414 main

    800.232.8913 toll free

    sagesupport@dwdtechgroup.com

    www.dwdtechgroup.com

     






  • 3.  RE: Payroll on its own installation, need to merge to another installation

    Posted 01-27-2022 17:04
    David
    Thank you.  So payroll will go with but in a separate company code.  
    Good idea,   Much better than my thought process!
    Hopefully, it'll let me migrate just the company code PRB.  Not sure if Sage will recognize system files haven't been migrated before.
    N

    ------------------------------
    Nancy Hanson
    Blytheco LLC
    Eagan MN
    ------------------------------

    Original Message


  • 4.  RE: Payroll on its own installation, need to merge to another installation

    Posted 01-27-2022 17:05
    I'd ask Elliott.Pritchard@sage.com ... He helped me merge historical PR data into a different system (leaving history as a separate company code), but the source PR data was before PR 2.0 conversion, with no PII encryption to deal with.
    Easiest plan: get the whole MAS90 folder from the accountants, and leave it alone in that form.  Run workstation install to access it as a stand-alone historical reference (not a merged system).

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



Related Content