User defined options to migrate Tax masters into Sage 300 ERP

This post was originally published on this site

User defined options to migrate Tax masters into Sage 300

GUMU™ for is a Sage certified Migration solution. Greytrix is a pioneer in providing Migration services at its Sage Migration Center and catering end-user business requirements. We at Greytrix are focused to help the client in successfully implementing the new Sage 300 ERP system through our various successful migration and integration solutions.

In this blog, we would discuss the User-defined options to convert Tax masters into Sage 300 ERP. We convert masters by using below-mentioned method from Sage 50 US (Peachtree), QuickBooks. In this blog, we have taken the example of Sage 50 ERP.

 New Stuff:  User-defined options to migrate Item masters into Sage 300 ERP  

In continuation of our previous blog here, we would discuss another method for Tax Number Generation referred as ‘User defined Mapping’. While performing migration process, we receive different requirement from clients to assign the specific numbering to Tax masters into in Sage 100 Company.

So in order to incorporate the custom numbering for Tax, we do send the template Tax number mapping sheet to our client before proceeding with the migration process. The format of the sheet is as below which contains the columns – Sage 50 Tax Number, Sage 50 Tax Name, Sage 300 ERP Tax Number and Sage 300 ERP Tax Name. We expect the filled sheet from client wherein he needs to fill their desired Tax masters code and their names as they want to get converted into Sage 300 ERP against the existing Sage 50 Tax details.

Once we receive the filled sheet from the client, we process them accordingly into migration and client’s desired Tax number gets assigned/created into Sage 300 and same gets assigned to their respective transactions.

In this way, Sage 50 Tax masters are migrated to target Sage 300 ERP company database.



You May Also Like

About the Author: AJ Amjad Khan

Leave a Reply

Your email address will not be published. Required fields are marked *