Create Import Entity Routine and Import data in GUMU™ New Pure Lightning Interface from Sage 100 ERP to Salesforce.

This Module allows users to import ERP Customers along with contact(s) into Salesforce Account(s) and contact(s). Also allows users to import product, product family and various tables’ data from Sage 100 ERP to Salesforce.

  1. Click on “GUMU Settings” tab to view “Entity Mapping/Import” Module on Administration page.

  1. Click on Entity Mapping/Import Module to import data. Refer the below Steps to import Customers from Sage 100 into Salesforce. To import data, here we took an example of “Customers” import routine:

  • The integration should be pre-selected if you have checkbox the “Default” on setup page.

  • Then select the Import Type from the list as shown in above screen (i.e. Import Customers/Import Products etc.). Refer below screen.

  1. Sync Now Button allows you import the customers from Sage 100 ERP to Salesforce.

  1. Once we are familiar with syncing of data from Sage 100 ERP to Salesforce, now we will learn how to create new import routine for a custom object being created in Salesforce. Here we are creating Import Routine for Invoice Object and we would be using the “Invoice Header” Entity created using Entity Setting Module in Salesforce through GUMU. To create new Import routine follow the below mentioned steps:

  • Login into Salesforce and go to GUMU Settings application.

  • Click on “Entity Mapping/Import” to create new import routine.

  1. On clicking the button it will direct the user to a page where they need to give the import routine a “Name” similar to Object in Salesforce for easy Identification, mention the “Object API Name” the object possess in Salesforce and select the “Entity” from which they want the data to be imported from Sage 100 ERP and do remember to tick the “Active” checkbox in order to use the Import Routine to sync data into Salesforce. Refer the below image:

  1. Now we shall proceed further to Mapp fields for importing data in Salesforce. Follow the below steps:

  • Click on the “Edit” button as show in the above image and click on “Refresh Fields” button and click on “Details” tab to Mapp the Salesforce Fields with Source fields of Sage 100 ERP to import data and click on “Save” button. Refer the below Image:

  1. Once you have mapped the field and saved the newly created import routine, it time to import data for the Object from Sage 100 ERP to Salesforce. To import data click on “Sync Now” button. Refer the below image:

Kindly follow the steps stated below in order to use filter functionality Import routine in Salesforce: –

  • Login to Salesforce Org.

  • Go to setup & navigate to app launcher and select “GUMU Settings” from app list.

  • Click on “Entity Mapping/Import” tab to view entity list page.

  • Select the entity for which you want to run the import routine and go to the “Details” tab.

  • Click on “Filter” tab to add filter.

  • Click on “Edit” button.

  • Click on “Add filter Row” button to add filter.

  • Select “Source Field” value from drop down, which shows all the fields of Sage 100 related to the API name.

  • Select “Operator” value from drop down.

  • Enter the “Value”.

  • Click on ”Active” to activate the filter.

  • Click on “Save”.

  • As shown in the above image we needed to add a filter in Order to import a specific product or any necessary details from Sage 100.

  • Source Field for the same is ‘Item code’, (please note that we can select any “Source Fields” value from drop down). Operator is “Equals” and Value is “8007” i.e. Item code value. Thus in layman terms it will read as “Import Code” source Field value is equals to 8007 if condition is met then product is imported in Salesforce.

  • If user wants to skip any unwanted data, they can change the operator with “not equal to”, then the specific data will be skipped.

Our GUMU™ Integration for Salesforce has launched a couple of new feature in its new version. One of the new key features introduced in GUMU™ is it enables user to Import and Export the Entity Mapping from the Entity Mapping/Import tab.

Earlier, if the user needed the mapping to be added to a different Org, they had to create it manually. But now user can Export routine from Sandbox to Production to get the results without much efforts.

Kindly follow the steps stated below in order to use Import/Export Mapping functionality in Salesforce: –

  • Login to Salesforce Org.

  • Go to App Launcher and select “GUMU Settings” from app list.

  • Click on “Entity Mapping/Import” tab to view entity mapping list page.

  • Select the entity mapping for which you want to export the file and click on “Export Mapping” button.

  • The selected Entity Mapping file will be available through download immediately as shown in below image.

If need be user can also Edit the data for any modification (adding or deleting) the data in the file. But for doing the same, user has to be well-versed with the technical names of the fields in the objects from both Salesforce & Sage systems.

  • Next step is to login to Production Org or any required Org and go to Entity Mapping/Import tab; there you need to click on upload button to upload the downloaded file to import the entity mapping into Salesforce(refer the below image).

  • After the file upload, user needs to clicks on “Import Mapping” button.

  • This will start the internal processing and once done user will is notified with a success message (as shown in the below image).

We hope you may find this blog resourceful and helpful. If you still have concerns and need more help, please contact us at

Important things to Note:

This functionality will import Name, Object, Entity, Size value along with Mapping and Relationship present in Header/Details tab. Additionally, User need to Schedule import routine and add filter criteria in Header/Details tab manually. Before importing file to another Org user need to make sure that both ERP system must be same; For e.g.:- It will not import the Sage 100 connected Entity file to Sage 300 connected Entity file because both are two different ERP systems.