Professional Documents
Culture Documents
Contents
Data
Tool
SOQL Using Workbench
and Don'ts in Migration
Best Practices Data Loader
-2-
Dos
The Data Loader can move data into or out of any type of record. When importing data, it reads, extracts, and loads data from comma separated
values (CSV) files. When exporting data, it outputs CSV files.
-3-
You need to load into an object that is not yet supported by webbased importing.
You want to be able to save multiple mapping files for later use.
-4-
-5-
Batch Size
Assignment Rule
Server Host
test.salesforce.com Sandbox
Timeout
Proxy settings
Start at row
-6-
login.salesforce.com Production
On receiving the Meta Data Documents for the Legacy System map them with the Force.com Meta Data/
Objects-Fields.
Verify the same before performing any Migration Task, to ensure correctness.
While migrating prepare the mapping document using Data Loader and store them for future references.
Auto-Mapping
Manual Mapping
-7-
Always record the Success- Error Files for any Migration task performed to evaluate the performance of the migration
task .
These success-error files can be used as references in future for any migration task performed for the same client.
When encountering errors check the error message on the error files. Rework on the same and perform the Migration
task again.
-8-
Select statements
IN
Equals
Contains
Not Equals
Like
-9-
Upsert is an API function that combines insert and update into a single call.
Upsert uses an indexed custom field or external ID to determine whether to create a new object or
update an existing object
- 10 -
CLI of Data Loader is used when a process is desired to be automated because the GUI
form of Data Loader requires human interaction to accomplish the tasks.
Command Line Interface of Data loader executes the data loader from the command
line.
It can perform all the operations that the GUI version is capable of like insert, update,
upsert, delete & export data. Additionally, it can also move data to and from a commaseparated variable file (.csv) to and from a relational database, such as Oracle or SQL
Server, that has a standard JDBC driver
- 11 -
process-conf.xml
database-conf.xml
(The XML files can be found at :
- 12 -
- 13 -
You want to prevent duplicates by uploading records according to account name and site, contact email
address, or lead email address.
Import Wizard
Schedule Imports
Export data
- 14 -
- 15 -
To access import wizards for organization-wide data, from Setup, select Data Management.
- 16 -
Before selecting the file to be imported, the CSV file has to follow a certain format, depending on the
object type being imported. Given below is an example for contacts.
- 17 -
After the format of the CSV file is as desired, the user is allowed to specify the following parameters
for the import.
- 18 -
The next step is to select the operation that is to be performed, i.e. insert, update or upsert.
- 19 -
The next step is to select which user field is included in the .csv to designate the record owners. Next you
upload the .csv
- 20 -
The final step is to edit the field mapping. Some fields will be already mapped; for the other fields you can
map manually.
Workbench Tool
Powerful web-based suite of tools designed for administrators and developers to interact with
Force.com organizations via the Force.com APIs
Users can describe, query, manipulate, and migrate both data and metadata in Force.com organizations
- 21 -
directly in their web browser with a simple and intuitive user interface
Accessing Workbench
- 24 -
Donts
EXTRACT /DATA Stores the source data from one or more Legacy Database/Force.com.
MAPPING Stores the mapping files for each object whose records are to be migrated to
Force.com.
LOAD Stores the final copy of the files to be uploaded into Force.com generated after the
transformations(if required) on the source data is complete.
STATUS (SUCCESS-ERROR) Stores the success & error files of each migration task performed
per object.
BACKUP Maintains the backup copy of the data in the target org.
- 25 -
QnA
- 27 -