Consolidating Multiple Salesforce Orgs with Integrate.io

Hi there. My name is Teri Morgan, and I'm a solutions engineer with Integrate.io. Lots of businesses store valuable information in Salesforce. Likely, your company is one of them.

Often, they need to move that data around within Salesforce. Perhaps you need to move data from one object to another. Maybe your company has more than one Salesforce instance, and you need to move data back and forth between them. I have even worked with large corporations where the parent company has one Salesforce and each of its portfolio companies has their own.

The parent company wants its Salesforce to be the one source of truth where they can run company wide reporting. Consequently, they need each of the portfolio companies' data synced in their Salesforce.

How would we do this? Let me walk you through a quick demonstration.

In Integrate.io, we would start by building a package.

This package is gonna be named Salesforce accounts because we're gonna be bringing in the account objects.

First, we need to add those Salesforce source components, one for each portfolio company.

This one is gonna be company one.

We'll select all the fields and save the component.

Now our parent company would like to add a company ID for each of these companies so that they can keep each of the datasets straight.

In Integrate.io, one of the best features is it's our transformation layer. Using the code free transformation components, customers can do everything they want from standard SQL unions, joins, clones, to parsing, hashing, or encrypting data even on a field level. We're gonna use the select component to add that company ID. We'll start by bringing in all of our fields.

K. And then we wanna add that extra field.

So for company number one, its ID will be one zero zero one.

Then we will save that. Now we need to duplicate these, one for each of the portfolio companies.

K. Then we're gonna go in and change change the source of that data so that it's specific to this portfolio company. This one is two.

There we go.

Now we've still got our account object.

We still got all those fields. Perfect.

Save.

This ID is going to be one zero zero two.

This is company three.

Its source of data will come from its Salesforce.

Still the account object, still those fields. Save it.

And its ID will be one zero zero three.

And finally, company four.

Select its data source.

Still the account object.

Still those fields.

And its ID, you guessed it, one zero zero four.

K. So now we need to combine these datasets.

We are gonna use this easy no code union component and combine the data from company one and company two.

Autofill all of those fields and save.

Now we're gonna do the same thing for companies three and four.

And finally, we'll union those two data streams together.

At this point, we're ready to send all of that data into the parent Salesforce instance.

We're gonna choose it's Salesforce.

Our target our target object is the account, and we're gonna upsert.

Bring in all of those fields.

We name this component, and we're gonna save it. So at this point, now we have a data pipeline built that will bring in all of the account objects from each of those portfolio companies and update the parent object with it.

Go ahead and save that.

We're gonna come back here to our package package editor. So we built that here.

Now we can come in and choose to duplicate that same package because maybe we wanna bring in not only the account object, but maybe we wanna bring in leads and opportunities.

So we're gonna rename these.

This will be our leads package.

This one this one will be opportunities.

Now at this point, you would need to go back into those packages and change the objects from accounts to opportunities and leads. But for the sake of time, we're gonna pretend that we've already done that. Now we would like to create a new package.

This is gonna be our Salesforce update package. Actually, let's name it Salesforce workflow because that's what it's gonna be. It's gonna be a workflow instead of a data flow.

In Integrate.io, a work flow, this feature allows us to add logic between multiple packages so that we can set up a series of packages to run successfully based on completion, based on failure.

And so we're gonna do that now.

We are gonna run our first package, and we select which package that is. We want let's say we want the accounts. This is gonna be our accounts package. We are gonna update the accounts first.

And then when that runs successfully, now we would like to update the leads next.

Once the leads is completed, we're gonna update opportunities.

So now we have each of these individual packages that will run-in succession. Let's save this workflow.

Now we're ready to schedule it so that it can just run automatically.

We'll create a new schedule for it.

Let's say that we want this package, this workflow to run every two hours.

That'll give us enough frequency so that so that our parent Salesforce can remain updated with all of the portfolio company's sales forces.

We'll add the workflow to this schedule.

Save that, and we're just gonna turn that turn that schedule on. Once we've created that, that will automatically start running and update every every two hours.

So, this is a pretty common use case that I come across. Most recently, I had a client that was in this same boat for the sake of his privacy. I'll call him Andy. Andy was really struggling with the amount of manual effort that he was spending in Salesforce. He was frustrated because he felt that his role wasn't adding value to the organization.

It got to a point where even his boss was questioning the amount of impact Andy was bringing to the company. He was terrified that he might lose his job in the next round of layoffs.

Fortunately, Andy solved his problem by automating the manual work he was doing in Salesforce by using an ETL platform.

By doing so, he was able to save fifteen hours of manual effort per week, which enabled him to devote more time to restructuring the reporting process his company used. This created a dramatic increase in his output, which he was able to concentrate on greater timeliness and accuracy in the reporting process.

There was so much improvement that after completing this project, Andy is now being considered for promotion.

I wish him the best of luck. He has my full support moving forward because I know this is a key element to their business.

If you think there's an opportunity for xPlanity to help you solve a similar problem, I'm more than happy to discuss it with you. Please reach out to me at xforcexplenty dot com. Thank you.

‍