Salesforce Org to Org Opportunity Migration

This template moves a large set of opportunities from one Salesforce org to another. You can trigger this manually or programmatically with an HTTP call.

Opportunities are upserted so that the migration can be run multiple times without worrying about creating duplicates. Parent accounts of the opportunities are created if they don’t already exist in the destination system, or can be set to be a specific account for all opportunities that are migrated. This template uses batch to efficiently process many records at a time.

License Agreement

This template is subject to the conditions of the MuleSoft License Agreement. Review the terms of the license before downloading and using this template. You can use this template for free with the Mule Enterprise Edition, CloudHub, or as a trial in Anypoint Studio.

Use Case

As a Salesforce admin I want to migrate opportunities from one Salesforce organization to another one.

This template serves as a foundation for the process of migrating opportunities from one Salesforce instance to another, being able to specify filtering criteria and desired behavior when an opportunity already exists in the destination org.

As implemented, this template leverages the Mule batch module.

The batch job is divided in Process and On Complete stages.

Migration process starts from fetching all the existing opportunities that match the filter criteria from Salesforce Org A.

On Process stage matched opportunities will be grouped and inserted or updated in Salesforce Org B.

Finally during the On Complete stage the template will both output statistics data into the console and send a notification email with the results of the batch execution.

Considerations

To make this template run, there are certain preconditions that must be considered. All of them deal with the preparations in both, that must be made for the template to run smoothly. Failing to do so can lead to unexpected behavior of the template.

Salesforce Considerations

Here's what you need to know about Salesforce to get this template to work:

• Where can I check that the field configuration for my Salesforce instance is the right one? See: Salesforce: Checking Field Accessibility for a Particular Field.
• How can I modify the Field Access Settings? See: Salesforce: Modifying Field Access Settings.

As a Data Source

If the user who configured the template for the source system does not have at least read only permissions for the fields that are fetched, then an InvalidFieldFault API fault displays.

java.lang.RuntimeException: [InvalidFieldFault [ApiQueryFault
[ApiFault  exceptionCode='INVALID_FIELD'
exceptionMessage='Account.Phone, Account.Rating, Account.RecordTypeId,
Account.ShippingCity
^
ERROR at Row:1:Column:486
No such column 'RecordTypeId' on entity 'Account'. If you are attempting to
use a custom field, be sure to append the '__c' after the custom field
name. Reference your WSDL or the describe call for the appropriate names.'
]
row='1'
column='486'
]
]

As a Data Destination

There are no considerations with using Salesforce as a data destination.

Run it!

Simple steps to get this template running.

Running On Premises

In this section we help you run this template on your computer.

Where to Download Anypoint Studio and the Mule Runtime

If you are new to Mule, download this software:

• Download Anypoint Studio
• Download Mule runtime

Note: Anypoint Studio requires JDK 8.

Importing a Template into Studio

In Studio, click the Exchange X icon in the upper left of the taskbar, log in with your Anypoint Platform credentials, search for the template, and click Open.

Running on Studio

After you import your template into Anypoint Studio, follow these steps to run it:

• Locate the properties file mule.dev.properties, in src/main/resources.
• Complete all the properties required as per the examples in the "Properties to Configure" section.
• Right click the template project folder.
• Hover your mouse over Run as.
• Click Mule Application (configure).
• Inside the dialog, select Environment and set the variable mule.env to the value dev.
• Click Run.

Running on Mule Standalone

Update the properties in one of the property files, for example in mule.prod.properties, and run your app with a corresponding environment variable. In this example, use mule.env=prod.

After this, to trigger the use case you just need to browse to the local HTTP endpoint with the port you configured in your file. If this is, for instance, 9090 then you should browse to: http://localhost:9090/migrateopportunities and this creates a CSV report and sends it to the emails you set.

Running on CloudHub

When creating your application in CloudHub, go to Runtime Manager > Manage Application > Properties to set the environment variables listed in "Properties to Configure" as well as the mule.env value.

Once your app is all set and started, supposing you choose as domain name sfdcOpportunitymigration to trigger the use case you just need to browse to http://sfdcOpportunitymigration.cloudhub.io/migrateopportunities and report is sent to the emails you configured.

Deploying a Template in CloudHub

In Studio, right click your project name in Package Explorer and select Anypoint Platform > Deploy on CloudHub.

Properties to Configure

To use this template, configure properties such as credentials, configurations, etc.) in the properties file or in CloudHub from Runtime Manager > Manage Application > Properties. The sections that follow list example values.

Application Configuration

HTTP Connector Configuration

• http.port 9090

Batch Aggregator Configuration

• page.size 1000

Account Sync Policy

• account.sync.policy syncAccount

Note: the property account.sync.policy can take any of the two following values:

• empty_value: If the propety has no value assigned to it, the application does nothing in respect to the account and just moves the opportunity over.
• syncAccount: Tries to create the opportunity's account if the account is not present in Salesforce instance B.

Salesforce Connector Configuration for Company A

• sfdc.a.username bob.dylan@orga
• sfdc.a.password DylanPassword123
• sfdc.a.securityToken avsfwCUl7apQs56Xq2AKi3X

Salesforce Connector Configuration for Company B

• sfdc.b.username joan.baez@orgb
• sfdc.b.password JoanBaez456
• sfdc.b.securityToken ces56arl7apQs56XTddf34X

SMTP Services Configuration

• smtp.host smtp.gmail.com
• smtp.port 587
• smtp.user sender%40gmail.com
• smtp.password secret

Email Details

• mail.from batch.migrateOpportunities%40mulesoft.com
• mail.to your.email@gmail.com
• mail.subject Salesforce2Salesforce Opportunity migration Report

API Calls

Salesforce imposes limits on the number of API Calls that can be made. Therefore calculating this amount may be an important factor to consider. The template calls to the API can be calculated using the formula:

1 + X + X / ${page.size}

X is the number of pportunities to synchronize in each run.

Divide by ${page.size} because, by default, opportunities are gathered in groups of ${page.size} for each Upsert API call in the commit step.

For instance if 10 records are fetched from origin instance, then 12 API calls are made (1 + 10 + 1).

Customize It!

This brief guide provides a high level understanding of how this template is built and how you can change it according to your needs. As Mule applications are based on XML files, this page describes the XML files used with this template. More files are available such as test classes and Mule application files, but to keep it simple, we focus on these XML files:

• config.xml
• businessLogic.xml
• endpoints.xml
• errorHandling.xml

config.xml

This file provides the configuration for connectors and configuration properties. Only change this file to make core changes to the connector processing logic. Otherwise, all parameters that can be modified should instead be in a properties file, which is the recommended place to make changes.

businessLogic.xml

Functional aspect of the template is implemented on this XML, directed by one flow responsible of excecuting the logic.

For the purpose of this particular template the mainFlow uses a batch job, which handles all the logic of it.

endpoints.xml

This file provides the inbound and outbound sides of your integration app.

This template has only an HTTP Inbound Endpoint as the way to trigger the use case.

Inbound Flow

HTTP Inbound Endpoint - Start Report Generation

• ${http.port} is set as a property to be defined either on a property file or in CloudHub environment variables.
• The path configured by default is migrateopportunities and you are free to change for the one you prefer.
• The host name for all endpoints in your CloudHub configuration should be defined as localhost. CloudHub will then route requests from your application domain URL to the endpoint.
• The endpoint is configured as a request-response since as a result of calling it the response will be the total of Opportunities synced and filtered by the criteria specified.

errorHandling.xml

This file handles how your integration reacts depending on the different exceptions. This file provides error handling that is referenced by the main flow in the business logic.