Sage 100

 View Only
Expand all | Collapse all

Migration 4.50 to 2017 to 2022

  • 1.  Migration 4.50 to 2017 to 2022

    Posted 07-09-2022 11:56
    I do the pre-migration and I have a few employees that I can not create, because the employee number still exists in another department.
    What is the workaround for that...

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------


  • 2.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-09-2022 12:00
    Renumber employees either in 4.5 or 2017.  Has to be done before 2018.  No duplicate employee numbers.

    ------------------------------
    Annette Egbert
    Acuity Solutions, LLC
    ------------------------------



  • 3.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-09-2022 12:00
    I try to renumber in 4.5 and it says that the employee number already exists in another department...

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------



  • 4.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-09-2022 12:06
    Or do you mean I have to renumber the ones that already exist so I can create the ones that are missings????

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------



  • 5.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-09-2022 12:11
    But I would backup a step and not migrate until all employees are accounted for.

    ------------------------------
    Annette Egbert
    Acuity Solutions, LLC
    ------------------------------



  • 6.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-09-2022 12:10
    If the number exists in another department, change the number being used.  Cannot reuse numbers.

    ------------------------------
    Annette Egbert
    Acuity Solutions, LLC
    ------------------------------



  • 7.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-09-2022 12:13
    that is what I just did....created a new company...and that is the one I will migrate...thanks.... hopefully it works

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------



  • 8.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-09-2022 12:33
    Very weird...in 4.50 I renumbered the ones that already existed to diff number but same dept.  Then I created the one that appeared on the pre-migration report.
    Went ahead and migrated to 2017 again, converted.  Now I run the pre-migration again and it brings me a list of new missing employees...another bunch of around 25????

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------



  • 9.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-09-2022 12:19
    I said that wrong, you can reuse the number, you just can't use the same number more than once.

    ------------------------------
    Annette Egbert
    Acuity Solutions, LLC
    ------------------------------



  • 10.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-11-2022 07:26
    I just found...after 48 hours in an upgrade, this utility....PR_EmpNoFix_Utl.   has anyone ever used it????

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------



  • 11.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-11-2022 07:46
    I hadn't heard of it either.  Appears to delete records that do do not have a number in the employee master.  Interesting.  Seems to be what you have been looking for all along.

    ------------------------------
    Jeff Schwenk
    Bottomline Software, Inc.
    ------------------------------



  • 12.  RE: Migration 4.50 to 2017 to 2022

    Posted 07-11-2022 14:45
    FYI, I had a call with Sage's Payroll consultant Alec today about my migration issues. 
    These are a few of the things I learned:
    1. You can upgrade from 4.50.8 directly to new framework without doing a v2017 migration
    2. The pre-migration report for missing employees is only a suggestion.  You are not required to enter them in the prior version.
    3. If on the migration they are not found, their history is ommitted.
    4. You only need to go over the list and decide which employees you would like to migrate, based on the last date, and create those.

    Don't you think the missing employee report should be sorted by last transaction date in descending order????  That would ease my upgrades inmensely.

    ------------------------------
    Lourdes Sobrino
    LU² DSD Puerto Rico
    Guaynabo Puerto Rico
    787.485.9638
    ------------------------------