Sage 100

Applies to Sage 100 2018+ ( 6.00) when you attempt to copy the MAS_XXX folder during a re-migration and conversion.

The issue is that MAS_SYSTEM has an AES key field ( per company ) which helps ensure data cannot simply copy.

Here's the workaround: 

Using DFDM, go into sy_company,  find the AES Encryption key for one of the current companies in the destination system.    I never bother with the "Change encryption keys" program, I just 

1. create the new company in the destination system, 
2. copy in the data, then 
3. grab the encryption key from a good company in and paste it into the AES encryption field of the new company.  Comes right up.

For version 610 ( 2019 )  (and maybe 600 - 2018 ), you will also need to go into the G/L options for a known good company and do the same for data encryption test.  That handles the PII stuff.  I think Payroll is like G/L, but I haven't fiddled with it.

Applies to Sage 100 2018+ ( 6.00) when you attempt to copy the MAS_XXX folder during a re-migration and conversion.

The issue is that MAS_SYSTEM has an AES key field ( per company ) which helps ensure data cannot simply copy.

Here's the workaround: 

Using DFDM, go into sy_company,  find the AES Encryption key for one of the current companies in the destination system.    I never bother with the "Change encryption keys" program, I just 

1. create the new company in the destination system, 
2. copy in the data, then 
3. grab the encryption key from a good company in and paste it into the AES encryption field of the new company.  Comes right up.

For version 610 ( 2019 )  (and maybe 600 - 2018 ), you will also need to go into the G/L options for a known good company and do the same for data encryption test.  That handles the PII stuff.  I think Payroll is like G/L, but I haven't fiddled with it.

Applies to Sage 100 2018+ ( 6.00) when you attempt to copy the MAS_XXX folder during a re-migration and conversion.

The issue is that MAS_SYSTEM has an AES key field ( per company ) which helps ensure data cannot simply copy.

Here's the workaround: 

Using DFDM, go into sy_company,  find the AES Encryption key for one of the current companies in the destination system.    I never bother with the "Change encryption keys" program, I just 

1. create the new company in the destination system, 
2. copy in the data, then 
3. grab the encryption key from a good company in and paste it into the AES encryption field of the new company.  Comes right up.

For version 610 ( 2019 )  (and maybe 600 - 2018 ), you will also need to go into the G/L options for a known good company and do the same for data encryption test.  That handles the PII stuff.  I think Payroll is like G/L, but I haven't fiddled with it.

Applies to Sage 100 2018+ ( 6.00) when you attempt to copy the MAS_XXX folder during a re-migration and conversion.

The issue is that MAS_SYSTEM has an AES key field ( per company ) which helps ensure data cannot simply copy.

Here's the workaround: 

Using DFDM, go into sy_company,  find the AES Encryption key for one of the current companies in the destination system.    I never bother with the "Change encryption keys" program, I just 

1. create the new company in the destination system, 
2. copy in the data, then 
3. grab the encryption key from a good company in and paste it into the AES encryption field of the new company.  Comes right up.

For version 610 ( 2019 )  (and maybe 600 - 2018 ), you will also need to go into the G/L options for a known good company and do the same for data encryption test.  That handles the PII stuff.  I think Payroll is like G/L, but I haven't fiddled with it.