Steps for Migration:
1. Download the template package .spkz file and save it to your desktop.
2. In the file Double click on the required object record to migrate(say for eg Account). This will open the Scribe WorkBench.
3. In the Scribe WorkBench we have to do the following step:
- Connect to the source and target databases
- Create data links
- Link source and target data fields
- Set up insert and update steps to control the data migration
- Save our work as a Data Translation Specification (DTS) file
- Test and Run the DTS
- Identify and fix errors using the Transaction Error Report
Before describing each of this steps we have to know what is DTS:
A DTS includes the following information:
- Connection information for the source and target data stores.
- Steps that define the data processing logic to be used when the DTS file is run.
- A mapping table that links fields in the source to the appropriate field in the target. This can include lookup links, data links, or fixed value links.
- Formulas used for conversion, parsing, or conditional import of selected source fields.
a) Connect to Source and Target Databases – To specify the source database, scroll through the list of sources available in the Scribe Workbench. We have to Login to ourSalesforce account to connect to it and choose the object. After specifying, the list of source data fields display in the source pane. Each field has an associated reference number (the REF field) which we can use in functions and formulas. Similarly for target we have to Login to the Microsoft Dynamic CRM account and define the steps to include in the migration. A step is an operation that is performed on a target data object. Steps are performed once for each source row. From the bottom of the pane, we have to select Update/Insert. Then the main window appears with both source and target fields.
b) Create data links and Link source and target data fields – We need to create data links to map the source fields to the target fields. Data links allow us to set values on target fields. One or more source fields can be linked to one or more fields in the target. Eg PHONE to PHONE, BUSINESS_NAME to ACCOUNTNAME. We can also use function and formula according to the requirement.
This will migrate the normal field values. But what about Lookup field(Related field) values? To overcome this we have to create a field(Salesforce ID) in the target object and create a data link as ID -> Salesforce ID.
In this newly created field the original salesforce ID is stored with the help of which the lookup has to be created in the Dynamic CRM. While migrating contact, two new fields have to be created(Salesforce ID,Salesforce Account ID) in Contact where we have to create data link as
ID -> Salesforce ID
AccountID -> Salesforce Account ID
In this way we can pass the look up values as well, such as after migrating account, when contacts are migrated then their associated accounts are also inserted by inner join. There is an option of inner join in the workbench which helped to identify those by linking these newly created Salesforce ID fields.
c) Lookup links – Lookup links allow us to define the match criteria when using seek, update, or delete steps.This link will be used by the update/insert step we just created to locate the account to be updated. It allows the duplicate check and allow us to know which target records to update.
d) We have to save the work as DTS file and Test the data by selecting test from the RUN Menu.
e) Finally we have to run the job. When the Run Complete window displays, we should notice that we have 15 successful inserts, but one failed insert. To figure out why one row failed, we have to click on Transaction Errors in the Run Complete window to open the Transaction Errors report from where we can find the errors and correct and rerun the job until the success occurs.
In this way we can migrate data from Salesforce to Microsoft Dynamic CRM through Scribe Insight.