If you have been following the "No-Code, One Day, Migration" posts.... This is the second blog post dedicated to "Step 2: Migrate to the "new" Salesforce." Why? It is hard! Moving connected Saleforce data is tough, especially when navigating all of the objects in the massive Salesforce CPQ package. Fortunately, we are almost there!
The last step of Data Migration is making a tiny tweak in a database in order to turn an active consumption schedule into an inactive consumption schedule so that we can insert it.
A quick summary of what we have done so far:
- Extract the "old Salesforce" to a H2 database
- Restored a bunch of metadata and data from the database to our "new Salesforc"
Today's plan:
Finish up the data restore then verify that the "new" Salesforce passes the same steps of the Billing Specialist Superbadge that the old Salesforce already passed! (AKA- Was my migration actually accurate?!).
Ready?
Let's go!
Data Migration 3: Consumption Schedules (continued)
They are tough to insert because you can not insert a consumption rate without a consumption schedule... and you can not insert an active consumption schedule. It's a loop, and the simplest fix was to pop into the database and change the Consumption Schedule to not be active.
If you are using the Trailhead Baby tools, there is a little "h2console" button that you can simply click! This pops up a browser where all you need is a password. Mine was 1234.
If you are are like me with zero database background.....
Here is how you edit a record in a database...
Step 1: Locate the record
From here, I pushed the consumption schedules using CopyStorm/Restore then popped into the Salesforce to activate them.
Now, all of my data and metadata from the original Superbadge org was in another org! How did I know? I logged in to a different Trailhead account in order to try to pass the Superbadge with my new org.
Here's a silly story: Salesforce must have thought I was trying to cheat the Superbadge- which makes sense because I essentially connected an org with all of the correct configuration to a Trailhead account then launched the superbadge. Salesforce did some sort of valuation which wiped most of the created data and metadata from my new org! I panicked for a minute, then just started the migration again with CopyStorm/Restore. The job setup was saved, so it was a simple as "click to start over."
After that... click, click, click - all of the way down to step 15! Of course, I could not 100% complete the superbadge with the new org because I did not have quote #15. (I did have quote #16 with the correct configuration) Curious as to why? There is not a way (that I know!) to manually change a quote number in Salesforce CPQ.
Migration accomplished - an Admin's no-code, one-day, Salesforce CPQ migration - with time remaining to go to the beach.
I am heartily impressed by your blog and learned more from your article. Thank you so much for sharing with us Data Migration in Salesforce.
ReplyDeleteNice information given by you, Thank you so much for sharing your knowledge. Visit here for SAP banking services in Malta
ReplyDeleteI was searching for migration. Thanks, admin, for sharing such wonderful content on this topic. Now I have got everything I need about it. Here’s another informative content skilled migration to Australia from Bangladesh you may find here more information.
ReplyDelete