Set Up Business and People Data Layers For Import

A Global Business & People layer allows Geopointe customers access to over 8 million global businesses and 100 million people, powered by Zoominfo. If you wish to import this data into your system, you must set up your system for importing first.

It is also important to note that you should also first purchase some data Import Credits

This document with walk through the steps of setup required to import the data. Links to next steps are provided at the bottom.


Before you build your data layer field mapping, there are some fields you need to create first to prevent headache later. When writing data into the Account or Contact standard objects, we will pre-populate the Salesforce standard fields. However, there is one custom text field you will need to create for any object you import into. You need to create a field to store the Global Businesses ID or Global People ID. This is the identifier that we receive from ZoomInfo.

We would recommend the following values for those field(s):

Global Businesses ID
Name/Label: Global Business ID
Data Type: Text
Length: 255

Global People ID
Name/Label: Global Person ID
Data Type: Text
Length: 255

If you need help creating this field, this Trailhead module can help you on your way.

You may want to consider creating some other additional fields as well, if they are valuable to your business. Here is a list of other fields that are not mapped to Accounts and Contacts by default.

Accounts (Global Businesses)

  • Primary Industry
  • Secondary Industry
  • SIC2
  • NAICS1
  • NAICS2
Contacts (Global People)
  • Company Name* (not necessary; this is typically filled in during the import and linked to a report)
  • Middle Name
  • Suffix
  • Management Level
  • Company Division Name
  • Highest Job
A list is provided below of all fields that are available for mapping. Remember, if you are using an object besides Contacts or Accounts, these fields will not be automatically mapped.

Mapping Business or People Data to Salesforce Fields

Before you can complete an import, you need to first map the data to existing Salesforce fields. That is completed in Geopointe Setup. Once there, go to the Geopointe Data Layer tab.

Click New.

The next screen will prompt you to give the import mapping a name and choose the data layer object you're importing from. For this example, the mapping was named Businesses as Prospect Accounts and the chosen object is Global Businesses.

Upon choosing the Geopointe Object, additional information will pre-populate below. For Global Businesses, it will default to Accounts. For Global People, it will default to Contacts. If you keep the defaults, standard fields are pre-populated for you. If you switch to a different object (Leads or a custom prospect object, for example), you will have to define those mappings yourself.

Only the Global Businesses (or Global People) ID is required; all other fields are optional. Select the custom field you created for the Global ID, and then fill in (or remove) any fields that are important to your business. Remember, if you don't map it, it won't get imported.

Note: If you skipped creating the fields above and don't have fields to write this information into, you will need to cancel out of this, create the fields, and start over.

Once these are filled in, down at the bottom is a place to enter Default Fields. While optional, this is a great way to set defaults, especially if you want to a distinguish this data from prospects mined via other sources. 

To add a default value, click Add Default Field, enter the text for that field into the box, and select the field on the right. For this example, the Account Source is being set to Geopointe Global Data.

Once all fields are mapped and defaults set, click Save. If you intend to import both businesses and people, make sure you create a data layer for both.

Activate Import Buttons

Before importing can begin, you need a button to click. While still in Geopointe Setup, click over to the Actions Tab. The Import People button is in the Point Actions and the Import Businesses button is in the List Actions.

To activate one or both, click on Edit. Check the box for Available (Web) and Save.

With a data layer saved, a field mapping ready and a button exposed, as long as you have credits, you are ready to start importing data!

Next Steps:

Any questions about the nuances of this functionality? Don't hesitate to open a support case.



What is the full list of fields that can be mapped for Global Business Data?
  • Name
  • Website Domain
  • Phone
  • Fax
  • Street
  • City
  • State/Province
  • Postal Code
  • Country
  • Primary Industry
  • Secondary Industry
  • Revenue
  • Employees
  • SIC Code 1
  • SIC Code 2
  • NAICS 1
  • NAICS 2
  • Global Business ID

What is the full list of Global People Data fields that can be mapped?
  • Company Name
  • First Name
  • Last Name
  • Middle Name
  • Salutation
  • Suffix
  • Job Title
  • Job Function
  • Management Level
  • Company Division Name
  • Phone
  • Email
  • Street (unique to the Person and may be different than the Business location)
  • City (unique to the Person and may be different than the Business location)
  • State/Province (unique to the Person and may be different than the Business location)
  • Postal Code (unique to the Person and may be different than the Business location)
  • Country (unique to the Person and may be different than the Business location)
  • Highest Job
  • Global Contact ID

(Geopointe Admins) What if I don't want all of my users doing these imports?
You can always change the user access on the buttons, or limit their import capacity in User Settings.

Why do I need the Global Businesses/People ID?
It's an important identifier from our provider. If you don't want to see it, Enterprise and Unlimited Salesforce users can hide it from page layouts.

Can I create more than field mapping for Businesses or People?
Absolutely! But consider it carefully. You'll want to use easily distinguishable names so that your users know which one to pick. Too many field mappings will quickly become confusing.