Mass Restore Salesforce Hierarchical Data

*See our Safe Harbor Statement below 

GRAX Restore tooling -

So I’m logged into the GRAX web console, and here I can go see that I have some recent archives of accounts. 

So we can go and see through the data viewer, here's an account, opportunity, and case that is no longer in Salesforce, this has been archived. 

So one of the simplest things to do is just restore a single account. So we can click on this and see a plan of what's going to happen. 

With this very simple tool, we're simply going to put the first account object back. We get a preview that we can see there's more underneath it, but we're actually going to restore one level at a time. 

This is a real world workflow for restoring one or two records. 

But more interesting is setting to restore the whole hierarchy at once. So I'm going to go ahead and turn that on, and we'll do a bigger archive of everything or restore of everything. 

So now I can go to the whole archive and hit restore. 

And what we're going to see here is that we're going to put back those 500 archives and all their children in one operation. 

It takes a second to show the plan for this restore, but the performance of this is significantly improved in the latest version of GRAX. 

Restore is all a workflow, so. Well, this is processing, you can leave this and come back later. 

And we can see when it's ready. 

This is going through all the backup data and the archive data, finding all the accounts, all its related objects in the hierarchy, building a big restore manifest to put the data back into Salesforce. 

OK, it's finally done, took a little while because we are putting 500 accounts back and 3,000 cases back, but we can see everything it's going to do and everything that's pending and review the data here. 

You can also export the data as a .CSV or a view manually before you put things in. 

But let's go through this. 

One of the other new features is field overrides, that’s something that happens a lot if you've archived data while ago and the schema has changed or Salesforce validations have changed, might have to come in and change the data and override some of the fields, as we put it back in. 

We don't have to do that in this example. 

So now just finished this workflow and hit restore. And we'll continue to watch the progress as this puts stuff back. 

We can see has expected it's slowly but surely putting first the accounts in, then the opportunity is underneath it. Once those are done, it'll do the contacts underneath that. 

And finally, when those are done, it should do the cases underneath that. 

Again, the performance to put all this data back is significantly improved in the latest version of GRAX. 

Well, it's almost done, the final step is post-processing. It put all the data back in and it's doing one more backup of all the data to make sure that the representation of everything in GRAX  is up to date. 

Cool, so it's done. You can see we put 5,000 records back in about four minutes. 

Then we can go look at one of these. 

And of course, we can always see the timeline of the information or the data in GRAX. 

First, it was backed up at this time, then it was archived at this time and it was stored at this time. And we can go review everything in Salesforce. And we'll see if the account is back in there with its contacts and opportunities and related cases. 

So, yeah, that's all the latest GRAX restore tooling workflow to put data back into Salesforce. Either one object at a time or the whole hierarchy. 

Thank you.

---

* Safe Harbor Statement Our presentation, website, and materials may contain “forward-looking statements” within the meaning of Section 27A of the Securities Act of 1933 and Section 21E of the Securities Exchange Act of 1934. We intend all forward-looking statements to be covered by the safe harbor provisions of the Private Securities Litigation Reform Act of 1995. Forward-looking statements generally can be identified by the fact that they do not relate strictly to historical or current facts and by the use of forward-looking words such as “expect,” “expectation,” “believe,” “anticipate,” “may,” “could,” “intend,” “belief,” “plan,” “estimate,” “target,” “predict,” “likely,” “seek,” “project,” “model,” “ongoing,” “will,” “should,” “forecast,” “outlook” or similar terminology. These statements are based on and reflect our current expectations, estimates, assumptions and/ or projections as well as our perception of historical trends and current conditions, as well as other factors that we believe are appropriate and reasonable under the circumstances. Forward-looking statements are neither predictions nor guarantees of future events, circumstances or performance and are inherently subject to known and unknown risks, uncertainties and assumptions that could cause our actual results to differ materially from those indicated by those statements. There can be no assurance that our expectations, estimates, assumptions and/or projections, including with respect to the future earnings and performance or capital structure of GRAX will prove to be correct or that any of our expectations, estimates or projections will be achieved. Numerous factors could cause our actual results and events to differ materially from those expressed or implied by forward-looking statements. All forward-looking statements should be evaluated with the understanding of their inherent uncertainty. The forward-looking statements included on our presentation are only made as of the date indicated on the relevant materials and we disclaim any obligation to publicly update any forward-looking statement to reflect subsequent events or circumstances. GRAX assumes no obligation for, and does not intend to update, any forward-looking statements. Any unreleased services, features, functionality, or enhancements referenced in a GRAX document, roadmap, blog, website, press release, or public statement that are not currently available are subject to change at GRAX’s discretion and may not be delivered as planned or at all. Customers who purchase GRAX should make their purchase decisions based upon features and functions that are currently available.