Sage 100

Do you mean copy all files instead of migrating?  I'm confused about your wording.

For a customer who is 3.71 using payroll:

1. Convert 3.71 up to 2023 
2. Each Sage 100 2023.x company coming from a non-payroll 2.0 ( as is the case here ) that has payroll must be converted individually - there is no "convert all."
3. As part of the payroll conversion in 2023, you are asked a series of questions which include but are not limited to mapping withholding codes for federal and state as well as assigning tax rules to earnings codes and some deduction codes ( where applicable )
4. Now the customer takes that data and wants to review it and check the tax computations for accuracy, etc.
5. When the customer accepts the data, you set another time for their go live
6. During this process, you again either migrate or copy the data files up to 2023 ( I believe either way you have the same issue)
7. During data conversion to 2023, you are again prompted to walk through the process of mapping tax withholding statuses, earnings, deductions, etc

My question is - has anyone developed a way so payroll 2.0 won't again prompt you for all the mappings during your final go-live? 

It's extremely likely that I've missed a step, or when I copied the MAS_XXX over the existing MAS_XXX something was overwritten. And if that's the case, I apologize in advance for my ignorance and that was the purpose of my original message ( to make sure I didn't miss a step ).

Do you mean copy all files instead of migrating?  I'm confused about your wording.

WAYYYYY back in the day when this was a major issue, someone posted a thread on which tables in the new PR framework needed to be saved/copied.  It was a great thread on the shortcut.

For a customer who is 3.71 using payroll:

1. Convert 3.71 up to 2023 
2. Each Sage 100 2023.x company coming from a non-payroll 2.0 ( as is the case here ) that has payroll must be converted individually - there is no "convert all."
3. As part of the payroll conversion in 2023, you are asked a series of questions which include but are not limited to mapping withholding codes for federal and state as well as assigning tax rules to earnings codes and some deduction codes ( where applicable )
4. Now the customer takes that data and wants to review it and check the tax computations for accuracy, etc.
5. When the customer accepts the data, you set another time for their go live
6. During this process, you again either migrate or copy the data files up to 2023 ( I believe either way you have the same issue)
7. During data conversion to 2023, you are again prompted to walk through the process of mapping tax withholding statuses, earnings, deductions, etc

My question is - has anyone developed a way so payroll 2.0 won't again prompt you for all the mappings during your final go-live? 

It's extremely likely that I've missed a step, or when I copied the MAS_XXX over the existing MAS_XXX something was overwritten. And if that's the case, I apologize in advance for my ignorance and that was the purpose of my original message ( to make sure I didn't miss a step ).

Do you mean copy all files instead of migrating?  I'm confused about your wording.

@Wayne Schulz - Link from five years ago.

Sage 100 - 90 Minds Thrive

WAYYYYY back in the day when this was a major issue, someone posted a thread on which tables in the new PR framework needed to be saved/copied.  It was a great thread on the shortcut.

For a customer who is 3.71 using payroll:

1. Convert 3.71 up to 2023 
2. Each Sage 100 2023.x company coming from a non-payroll 2.0 ( as is the case here ) that has payroll must be converted individually - there is no "convert all."
3. As part of the payroll conversion in 2023, you are asked a series of questions which include but are not limited to mapping withholding codes for federal and state as well as assigning tax rules to earnings codes and some deduction codes ( where applicable )
4. Now the customer takes that data and wants to review it and check the tax computations for accuracy, etc.
5. When the customer accepts the data, you set another time for their go live
6. During this process, you again either migrate or copy the data files up to 2023 ( I believe either way you have the same issue)
7. During data conversion to 2023, you are again prompted to walk through the process of mapping tax withholding statuses, earnings, deductions, etc

My question is - has anyone developed a way so payroll 2.0 won't again prompt you for all the mappings during your final go-live? 

It's extremely likely that I've missed a step, or when I copied the MAS_XXX over the existing MAS_XXX something was overwritten. And if that's the case, I apologize in advance for my ignorance and that was the purpose of my original message ( to make sure I didn't miss a step ).

Do you mean copy all files instead of migrating?  I'm confused about your wording.