Migrating Custom Fields in Sage 300 ERP

By | July 30, 2015

GUMU TM for Sage PRO ERP to Sage 300 ERP is a Sage certified Migration solution. Greytrix is a pioneer in providing Migration services at its Sage Migration Centre and catering end-users business requirements.
We at Greytrix help the end –user in implementing new Sage 300 ERP system through our various successful migration and integration solutions.
Custom fields are used to store information about an entity and can be very essential for a company’s day-to-day business.
There might be times when some fields from source ERP cannot be mapped to fields in the target ERP. Sage 300 ERP allows to store such fields which are not in present in the standard Sage 300 ERP system as optional fields.
In this blog we will discuss about how custom fields can be populated in Sage 300 ERP (Formerly known as Accpac) from a source ERP using GUMU TM.
New Stuff: Migrate Vendor from Sage BusinessWorks to Sage 300 ERP
Below is a screenshot of an item in Sage PRO
PRO Item
 
In the above screen shot of Sage PRO system’s Item master screen, the Bar Code field has a value of ‘12345’ and there is no standard field in Sage 300 ERP to which this field can be mapped. Hence this field can be converted as optional field in Sage 300 ERP.
Below is a screenshot of the converted Sage 300 ERP data
Accpac
 
The above screenshot shows the converted barcode field in Sage 300 ERP with of ‘12345’ same as in Sage PRO system.
In this way, custom fields from Sage PRO ERP are migrated into target Sage 300 ERP company database. For more information on ERP data migration, drop us a mail at erpmig@greytrix.com
Also Read:
1) Migrate Sales Order from Sage 50 (US) to Sage 300 ERP
2) Migrate Sales Person from Sage 50 (CAD) to Sage 300 ERP
3) Migrate Items from Sage 50 (CAD) to Sage 300 ERP
4) Migrate GL Accounts Transactions from Sage 50 US to Sage 300 ERP
5) Migrate Purchase Orders from Sage 50 (US) to Sage 300 ERP