Preparing Salesforce for Data Migration

Before we can migrate data to Salesforce, we need to do a little Salesforce preparation work.

If you are not yet familiar with Salesforce, then I would strongly recommend reading the short article on Salesforce, which should get you going.

Salesforce User Account

Of course, to do anything with Salesforce, you will need a Salesforce user account. If you are using your own Free Salesforce Developer Environment, you will already have this covered; however, if you are using your Organisation’s Salesforce environment, then now is a good time to ask your Salesforce Administrator to create a new account.

This Salesforce account that you use for data migration should not be your own personal account. It should be an account that is specifically designated for data migration, for example, an account named “data.migration@…”.

Once you have your Salesforce username and password, you will also need a Security Token. Security Tokens are always required (and are appended to your password), when you are connecting to Salesforce using the SOAP API (as Talend does).

Salesforce Object Permission

You will need the correct access permission on all of the objects and fields that you want to work with.

Again, if you are using your own Free Salesforce Developer Environment, you will already have this covered; however, if you are using your Organisation’s Salesforce environment, then now is a good time to, again, ask your Salesforce Administrator for access permission on the objects and fields that you will be using.

These tutorials assume that you are working within your own Free Salesforce Developer Environment and that you will have administrator permission, meaning that you have full rights on all objects.

Although it is convenient to run with administrator permission this is, of course, a very bad idea; especially as you move through your environments, up to Production. Your data migration account should have the lowest access rights that are needed to complete the job, and these should be scaled back or removed once the data migration has been completed.

For the tutorials on this site, you will need read/write access to the following Sales Objects.

Campaign
Lead
CampaignMember
Account
Contact

A full discussion on Salesforce Object Permission is outside the scope of this tutorial.

External IDs

We are going to create some External IDs on some of our Salesforce Objects. If you have not already done so, take the opportunity to read the article on Salesforce Custom Objects and Fields.

It is likely, within your own Organisation, that you will have a Salesforce Administrator and you will be delegating the creation of these External IDs to your administrator.

To support our example data migration to Salesforce, we’re going to need the following External IDs, so create these now.

Object      Custom Field Name     API Name     Type     Length
Campaign    UUID                  UUID__c      Text         36
Lead        UUID                  UUID__c      Text         36
Account     UUID                  UUID__c      Text         36
Contact     UUID                  UUID__c      Text         36

Create these Custom Fields, with following attributes: –

Data Type          Text
Field Label        UUID
Length             36
Field Name         UUID
Required?          False
Unique?            True
External ID?       True
Case Sensitive?    True

When you create a Salesforce Custom Object or Field, the suffix “__c” is automatically appended to the API Name.

Next Buton