Tag Archives: salesforce cpq

An vector diagram depicting running a Salesforce CPQ deployment

How to Easily Run a Salesforce CPQ Deployment

Learn how to easily run a Salesforce CPQ deployment using Prodly’s automation templates. It takes 80 percent less time than manual deployment—while simultaneously eliminating errors.

Automate Salesforce CPQ Deployments

Few of us get excited about tedious manual labor. That’s why Prodly created the first DevOps tool for Salesforce CPQ to automate what is otherwise hours of manual, error-prone work. 

Here’s how to easily run a Salesforce CPQ deployment with Prodly’s automation:

  1. Select where the ready-to-go changes are and where they need to go—whether that’s the next org in your release path or a branch in your repository.
  2. Select whether all of CPQ needs to be deployed or just a part of CPQ (i.e. all Price Rules or a new Product)
  3. Deploy.

Prodly’s Salesforce CPQ Automation Features

Proven Templates for the Entire CPQ Configuration Data Model

Prodly DevOps comes with data set templates—think prebuilt automations—that capture the entirety of the Salesforce CPQ configuration data model. That means you can be up and running in no time. Our templates have been battle tested on over 55 million CPQ deployments.

All you have to do is make your CPQ changes in your development org, select the appropriate template—and Prodly DevOps does the rest for you. It knows all the parent-child relationships and selects them automatically for deployment. You can even deploy the entire CPQ configuration in one click using our automation templates.

Customize Data Set Templates

If you like, you can even customize data set templates to add additional relationships with configuration data.

By going deeper into the data set templates, you can get really granular as to what you want to deploy and what not. Then you can preview the deployment to make sure it has everything you need in it—and nothing else.

Temporarily Deactivate Platform Events in Salesforce

Many of our customers say their favorite feature in Prodly DevOps is the ability to temporarily deactivate—and, importantly, reactivate—platform events and automations like Validation Rules and Flows during a deployment.

While great for running your business and maintaining data hygiene in your org, these events can cause unnecessary and frustrating deployment errors during the development process. Prodly DevOps automatically reactivates the events when the deployment is completed.

Prodly’s ability to automate this during a deployment saves you heaps of time compared to manually turning events on and off. Plus, it ensures you don’t overlook an event—which could have serious consequences.

For example, if you forget to reactivate a Validation Rule, it could result in bad data being entered into the system. Or if you forget to reactivate a Flow, it could mean that a critical part of a business workflow doesn’t get executed.

Progress Report

Prodly DevOps shows you in the UI how the deployment is progressing, and it sends you an email notification when it’s complete. That way, you don’t have to keep an eye on it yourself.

Audit History

Does governance and SOX compliance keep you or your management up at night? Prodly DevOps provides automatic change tracking that provides an audit report of every change. This easily-generated audit report includes who made what changes, when, and why—and it can easily be sent, too. Your next SOX audit will fly by.

Promoting CPQ Configuration Data Changes Without Prodly

Without automation, deploying a change to your product catalog or other configuration data in Salesforce CPQ can be a complicated, painstaking, and time-consuming process.

For every root object, you have to migrate all the related objects–so both the parent and child objects—to ensure the configuration changed works when it is deployed to production.

Let’s say you’ve made changes to your Product object, which has dozens of parent and child relationships.

When you have to move the newly-configured Product records from your Developer sandbox or scratch org to integration, you also have to move related records in all those parent and child objects. And because Salesforce record IDs change between environments, you’ll need to map IDs to maintain those relationships.


For every single record. One object at a time.

Then you have to do it again when you move the changes to UAT. Manually. For every single record. One object at a time.

And again when you move them to staging.

And again when you promote them to production.

How long does this take? Hours, if not longer. Oh, and that’s assuming everything went according to plan and there weren’t any errors that required a do over.

The Market-Leading Salesforce CPQ DevOps Tool

See how easy it is to run a Salesforce CPQ deployment with Prodly DevOps compared to without?

Prodly is truly the best-in-class DevOps tool to enhance the benefits of Salesforce CPQ, and it offers even more brilliant features than described above! Our state-of-the-art platform includes work management integration, version control, effortless work deployment, and easy compliance. 

Getting up and running is a breeze—and super fast. Plus, if you have any questions at all, our support team is rated one of the best in the industry.

Discover how Prodly DevOps can streamline your Salesforce CPQ instance and accelerate your digital transformation!

A photo that complements the benefits of implementing salesforce cpq

The Benefits of Implementing Salesforce CPQ

In this blog, we explain that implementing Salesforce CPQ is more efficient than a manual CPQ system because it costs less time, minimizes manual work, and eliminates errors.

It streamlines the sales process, improves the customer experience, gives your sales team more time, and, as a result, increases revenue. In addition, it offers a more scalable solution that can grow along with your business.

A photo that complements the benefits of implementing salesforce cpq

Advantages to Implementing Salesforce CPQ

Implementing Salesforce CPQ, an automated system for generating quotes in Salesforce, offers many benefits when compared to using spreadsheets or a homegrown system.

Enhanced Efficiency

The manual use of spreadsheets or a system that’s cobbled together from multiple different processes for CPQ is highly inefficient. Why? Because it’s labor intensive, time consuming, and prone to error.

In contrast, Salesforce CPQ automates the configure, price, quote process in one powerful app.

It automatically narrows down product selections for customers to those that are most relevant based on factors such as need and company size. It helps sales reps with any additional configurations. Plus, it can even suggest fitting add-ons like extended service contracts, extra training sessions, or complementary products.

Because you’ve entered your standard pricing into Salesforce CPQ, the app provides guidance for sales reps to add package or line-item discounts. It can even be configured so you can enter a client’s budget and the software automatically generates matching product discounts. As a result, you can create quotes that capture better value.

Salesforce CPQ also generates a customer-ready quote that can include your branding, cover letters, specific T&Cs, and marketing materials.

More Streamlined Sales Process

According to Salesforce, using CPQ software results in:

  • 10 times faster quote generation thanks to automation
  • 95 percent reduction in approval time due to automatically enforced business rules for pricing and configuration
  • 2 times faster moving from quote to cash because sales reps can move faster
  • 30 percent quicker ramp up for new reps thanks to the use of a single automated process

Clearly, the sales process is significantly streamlined compared to using a manual method.

Improved Customer Experience

The customer experience is significantly improved. Why? It’s significantly faster to generate an accurate quote with any additional offers or product suggestions that apply.

So there’s less time between the customer’s exploration of the product and their receiving of an indication of the cost. This shortened time period keeps the momentum going.

At the same time, the customer receives a correct, automatically-generated, branded quotes that contain all the terms and conditions. It’s not a document with text that’s cut and pasted from a bunch of other sources. Instead, it’s a standardized contractual document that has been reviewed and approved before it goes to the customer.

More Time for Your Sales Team

With the automation offered by Salesforce CPQ, your sales reps spend less time on creating accurate, professional quotes and proposals. This means they have much more time to prospect, generate leads, and close more deals.

Scalability and Flexibility

To ensure smooth business growth, you need a CPQ solution that scales along with your CRM—like Salesforce CPQ. Because Salesforce CPQ is a Salesforce-native app, you don’t have to worry about upgrading the integration with your CRM.

Moreover, Salesforce CPQ is highly flexible and lets you easily customize it to add new features and products when needed.

Increased Revenue

We discussed how Salesforce CPQ gives your sales reps more time to prospect and generate leads, as well as a significantly shorter sales cycle. As a result, your business can see a significant increase in revenue. 

Plus, because Salesforce CPQ is cloud based, it’s accessible from anywhere. This provides sales reps with more freedom to generate quotes and close deals on the move.

In addition, by spending less time on the CPQ process thanks to automation, you can reduce your operational costs.

Enhance Your ROI With a Salesforce CPQ DevOps Tool

You can increase your revenue even more by automating the change management process in Salesforce CPQ with Prodly DevOps. Prodly’s state-of-the-art automation minimizes the manual work associated with data and configuration data migration and integrates seamlessly with DevOps Center. 

Using our Salesforce CPQ DevOps tool, you can deploy work 80 percent faster, reduce operational costs, and increase productivity.

Moreover, Prodly offers 1-click scratch org creation and sandbox seeding, built-in work management, and sandbox management. It provides automatic audit trail creation, as well as version control integration with GitHub, GitLab, Azure, and soon Jira. All this together make it the most effective end-to-end DevOps platform for Salesforce—all managed through a single pane of glass.

Discover Prodly DevOps for yourself—request a demo!

Streamline Salesforce CPQ deployment

Prodly Boosts Salesforce CPQ Data Deployment

In this blog, we explain how Prodly accelerates your Salesforce CPQ data deployments.

Boost Salesforce CPQ Deployments

With Prodly, you can quickly and easily deploy Salesforce CPQ data to production.

Created by the team that developed Salesforce CPQ, Prodly is the # 1 data migration tool for Salesforce. It streamlines the process of deploying Salesforce CPQ configuration data for seamless release management. 

With Prodly, you can deploy changes 66 percent faster than other solutions. What’s more: You can ramp up productivity by an astounding 80 percent!

Prodly streamlines Salesforce CPQ deployments because it offers several distinct benefits for users.

Streamline Salesforce CPQ deployment

Its Algorithms Are Optimized for Salesforce CPQ Data Migration

We’ve been perfecting our data deployment algorithms since 2015. Although Prodly was originally developed as a tool to streamline Salesforce CPQ deployments, we’ve developed our tool so it can be used with any Salesforce application. It’s still our core focus and main product.

It’s also important to note that we’re the only company in this space that originally focused on data. Other companies began with metadata and have only recently started to build out their data capabilities. As such, Prodly’s data migration capabilities are much more advanced.

It Provides Full Support for Any User From Start to Finish

Prodly is extremely user-friendly. It’s easy to navigate for admins and revenue operations, yet robust enough for developers. It’s a “clicks, not code” tool with a powerful DX plugin that allows you to move all data within Salesforce, without limits. 

Prodly offers fully automated data deployments, even for highly complex, Salesforce CPQ object models. It automatically determines the correct sequence for multi-object data loads. You don’t need any knowledge of CPQ schema, so everyone on your team can use the tool.

It Knows Which Records to Insert and Which to Upsert

Prodly makes sure your data upserts correctly. Automatic record matching understands the relationships between your records and maintains them in the destination org. This prevents duplicates. 

Recursive processing takes multiple passes through the data to make sure it updates with the correct information. Sometimes this requires the addition of a temporary value so the record can upsert. Later, Prodly goes back and updates the record to the real value.

For example, Price Rules of the type “Custom” require child conditions. So Prodly is smart enough to create Price Rule records in the default type and insert child condition records. Then it goes back and updates the Price Rule records to Custom.

With Lookup relationships and hardcoded IDs, Salesforce stores a record ID. This record ID changes in the destination org, which breaks the relationship between records. Prodly determines which record matches in the destination org and simply updates the IDs accordingly.

It Offers Superior Functionality for Every User Without Compromising Ease of Use

Prodly is completely reliable for Salesforce CPQ deployments. The Diagram View allows non-technical users to easily see what’s being moved. You control all settings down to the field level with a single click. 

It provides pre-built templates that empower you as your needs mature. You can even customize the templates so they’re specifically geared towards your needs.

It Offers Peace of Mind During Development From Start to Finish

Prodly lets you securely move any data to any org within Salesforce. It provides one-click data masking, as well as automatic duplicate, override, and error prevention. 

Prodly also offers easy Git integration for source control because it’s critical for commerce businesses to be SOX compliant,  This helps you enhance your governance and release process with version control.

When to Choose Prodly for Salesforce CPQ Deployments

Prodly is best used when you need to migrate large volumes of highly complex relational data. This occurs frequently in Salesforce CPQ. Just consider how often you need to make changes to reflect factors like seasonal promotions, sales in new territories, etc. And then consider across how many different products or artifacts you need to make those changes.

Clearly, you need a powerful Salesforce CPQ deployment tool that lets you focus on making the changes to the data. 

To see Prodly in action, request a personalized demo. 

The problem with Salesforce CPQ configuration data deployment

The Problem With CPQ Configuration Data

In this blog, we’ll examine the issue with deploying Salesforce configuration data and discuss why deploying metadata is easier. We’ll explain why Salesforce managed packages use configuration data in the first place—plus, we’ll mention how to streamline Salesforce CPQ configuration data deployment.

The problem with Salesforce CPQ configuration data deployment

The Issue With Deploying Configuration Data in Salesforce

Configuration data, or reference data, achieves a specific functionality in a Salesforce app. It’s like metadata in that it describes how the system behaves. However, it’s stored as transactional data in Salesforce’s databases. 

Because Salesforce doesn’t have tools to manage reference data, it’s critical for Salesforce CPQ users to understand why it exists and how it works.

It becomes particularly challenging when you need to promote many changes with complex relational data from a sandbox to production. You can’t use change sets, because they only work for actual metadata types.

You can use Data Loader–but that can be a laborious, lengthy, and painstaking process. Especially when you have a high volume of complex relational data, like in Salesforce CPQ, you can spend hours mapping objects. And that’s before mistakes and do-overs.

Why Is Migrating Metadata Easier?

In Salesforce, metadata is native to the platform. Salesforce can create new types of metadata when needed and has hundreds of types of metadata to power its applications.

For example, Salesforce created Einstein bots—with dialog as a new custom metadata type within the platform. 

Once the dialog was added as a metadata type, customers could develop their own bots in a sandbox. Then they could define the bots’ interactions with end-users based on the dialog metadata provided. 

Now, when they wanted to deploy those bots from a sandbox to production, they could simply use change sets. Why? Because the metadata types are already included in org migration tools that the platform provides. 

Why Does Salesforce CPQ Use Configuration Data?

If deploying metadata is relatively easy, why do some Salesforce apps use configuration data?

The answer is simple. Many apps are made by Salesforce App Partners (otherwise known as ISVs) who don’t have the ability to create new types of metadata. So when they want to specify behaviors in their applications, they need a solution. That’s where configuration data comes in.

Configuration data are records that serve as the code used by managed packages to produce some type of application behavior for applications built on Salesforce. 

For example, Salesforce CPQ is an AppExchange product originally created by Salesforce App Partner, Steelbrick. Even after Salesforce acquired Steelbrick, you still need to install the CPQ managed packages in your org to gain access to its many powerful features and functionalities.

One of these functionalities is Price Rules—conditions and actions that update prices. However, when Steelbrick developed Price Rules, it wasn’t an option to create a new type of metadata like with our Einstein dialog example. So they needed a different solution. 

Instead, they developed Price Rules as a custom Object made with configuration data. 

However, when you, the user, make changes to Price Rules, you can’t use change sets to promote those changes to production. Because they’re configuration data, you need to promote them as data.

Read Prodly Accelerates Salesforce CPQ Data Deployment to discover how to do this quickly and easily. 

Version control in Salesforce

What Is Version Control and What Are Its Benefits?

A version control system (VCS) tracks and manages the changes you make to your data and configuration data. It’s critical to managing changes in low-code Salesforce apps that use complex configuration data, like Salesforce CPQ and Field Service Lightning. 

A VCS offers many benefits, including faster iterations and configurations, improved collaboration within teams, and enhanced compliance. 

Version control in Salesforce

What Is Version Control?

Ever wish you could roll back changes you just made to your production org in error? How about being able to track the revision history of your changes over time?

Version control (also known as revision control or source control) is a methodology that resolves data control and management scenarios like these.

A VCS tracks and manages the changes you make to your data. In Salesforce apps that use configuration data, tracking changes as you move the data from Developer sandbox to QA to UAT to production is paramount. 

Especially in DevOps, where your changes occur fluidly, dynamically, and rapidly, version control is an essential component of configuration data management. That’s why it’s increasingly becoming a necessary element of the release management process.

The Benefits of Prodly With Version Control

Prodly with version control makes agile development a reality for complex, low-code Salesforce apps. Unlike other version control offerings for Salesforce, Prodly manages your configuration data, which makes it perfect for Salesforce CPQ, FSL, Billing, and B2B Commerce.

Prodly version control combines the power of Salesforce orgs and VCS branches. Using Prodly version control as your single source of truth has the following benefits when compared to traditional in-org development:

  1. You can iterate and configure faster in a truly agile environment.
  2. It improves collaboration within and amongst teams.
  3. You can ship complex configuration features faster.
  4. You can identify conflicts head on.
  5. It provides a full change history and audit trail.
  6. It allows you to maintain SOX compliance.
  7. You can easily roll data back to prior states.

How Does Version Control Work in Salesforce?

Version control in Salesforce works like this:

The initial master data commit retrieves your configuration data from your Salesforce production org and stores it in the VCS. At that point, the data in the VCS becomes your single source of truth. Going forward, you initiate all changes to data in your production org through the VCS.

A version in the VCS is a snapshot of your data at a given time. You check data out of the VCS, update it, and check it back in, creating a new version against which further changes are made. Then, if needed in the future, you can roll back your data to any version.

The VCS records all the changes you make so you can easily roll back to an earlier version if necessary due to a bug. At the same time, this change tracking creates an audit trail you can use for compliance purposes.

Does the VCS Replace My Deployment System?

You might be wondering whether the VCS replaces your deployment system. The short answer is no, it does not. 

The VCS works in conjunction with your deployment system through a concept called branching. A branch is a snapshot of your data created in the VCS and then deployed to a separate Salesforce sandbox or development org. 

Similar to how you likely work now, you develop your new features in the separate org to protect the data in your production org. When you’re ready, you check the changes back into the VCS branch, merge the branch back into the master, and deploy the changes to your production org.

To learn more about Prodly, request a demo.

Salesforce quote-to-cash process

Prodly CEO Max Rudman Featured on CPQ Podcast

Prodly CEO Max Rudman was recently interviewed by Frank Sohn, the host of CPQ Podcast.

CPQ Podcast, created by Novus Consulting, is dedicated to all things configure, price, quote. It shares insights on CPQ tools and processes by talking with industry leaders.

Prodly CEO Max Rudman as an Entrepreneur

In his conversation with Sohn, Max talks about how he caught the “entrepreneurial bug” and started working in CPQ. He discusses the beginnings of SteelBrick, which was later acquired by Salesforce and became Salesforce CPQ.

Expert Advice on Salesforce CPQ

Max talks about the difference between CPQ and quote to cash; plus, he offers advice on implementing Salesforce CPQ for businesses considering adding it to their app lineup.

Salesforce quote-to-cash process

Max also touches on the most common reasons he sees CPQ fail in businesses. Lastly, he explains why he joined the Prodly team , as well as Prodly’s goals for the future of empowering admins with effective and agile reference data management.

Check out the podcast here:


Max Rudman, CEO of Prodly

Max Rudman, Founder of SteelBrick, Appointed CEO of Prodly

Max Rudman, former Vice President of Salesforce CPQ and Founder of SteelBrick, has been appointed Chairman and CEO of Prodly. He joins the leadership team of David Belove, President and Chief Revenue Officer, and Daniel Rudman, Founder and Chief Technology Officer.


Max Rudman Has an Impressive Track Record in Enterprise Software

Rudman is a seasoned entrepreneur with a track record of success in enterprise software. He founded SteelBrick, a quote-to-cash company that became Salesforce CPQ after its acquisition by Salesforce in 2015.

Max Rudman, CEO of Prodly

He consequently served as Vice President of Salesforce CPQ for three years. Here he was instrumental in growing the customer base by 1000 percent and revenue by 2000 percent.  

Prodly’s Expanded Leadership Team Continues Acceleration Into Salesforce Ecosystem

Leveraging the combined expertise of the executive team, Prodly will advance the company’s market leadership. It will also accelerate its growth within the Salesforce ecosystem.

“The time is right for Prodly to take advantage of the transition underway from code-based to reference-data based enterprise applications,” said Max.  “It’s easier to configure and maintain reference-data based apps. However, unlike with with code-based development, there’s a lack of infrastructure to support agile reference data development. Prodly aims to fill this gap.”

Max and other Prodly executives will be at the Salesforce World Tour Boston on April 3rd. Meet with Prodly to learn more about its reference data management (RDM) solution for Salesforce CPQ, Field Service Lightning (FSL), Advanced Approvals (AA), and Billing applications.  Prodly simplifies and automates the arduous process of deploying reference data from one Salesforce org to another. 

Accelerate Salesforce

Accelerating Salesforce Application Implementations

Prodly, Inc. and Code Zero Consulting have signed a partner agreement aimed at accelerating Salesforce® application implementations. (Code Zero Consulting is now ATG Cognizant.)

Salesforce Partner Accelerating Salesforce Implementations With Prodly

Code Zero is an Atlanta-based Salesforce implementation partner specializing in enterprise-level, complex application implementation projects. Prodly, based in San Francisco, is the creator of the premier data migration application for the Salesforce ecosystem.

Code Zero will use Prodly to develop and install complex reference data sets in applications like Salesforce CPQ and Billing for their clients. Once Code Zero have completed an application implementation project, they’ll train clients to update their reference data with their own instance of Prodly.

Reference data configuration, testing and installation, and metadata configuration are crucial elements of implementation for most complex enterprise applications. Prodly automates this tedious, complicated process, significantly accelerating Salesforce application implementation time. This saves time, eliminates human error, and allows highly-skilled architects and developers to focus on more value-adding activities.

Accelerate Salesforce

Rob Freeland is the Co-Founder and Managing Principal of Solutions of Code Zero. He explains they decided to partner with Prodly after successfully using the tool for several client projects over the past year. “Prodly simplifies a very difficult process and makes it more repeatable and controllable,” he said.

Prodly CEO Dave Belove explains that Code Zero’s technical and business expertise and strong relationships with enterprise-level Salesforce customers make it an ideal match for Prodly. “Code Zero will introduce our data migration solution to sophisticated clients that absolutely need it,” he said. “This relationship provides tremendous leverage and exposure for us.”

The two teams were originally introduced to one another by Seamus Egan, Senior Partner Manager for Salesforce Quote-to-Cash.

Code Zero

Code Zero, now ATG Cognizant, is a cloud-focused consulting, IT systems development, and software integration provider. Founded by highly skilled executives, architects, and developers, their team has decades of experience. 

They’ve worked on everything from simple projects to the most complex, ambitious integrations in high technology, manufacturing, healthcare, media, telecommunications, and consulting.

A Silver Salesforce Partner, Code Zero helps clients quickly adapt to changing technology. It does this by focusing on elegant, efficient, and scalable solutions that maximize operational value and minimize long term costs.


Streamline Salesforce implementations

Streamlining Salesforce CPQ Implementations

Streamlining Salesforce CPQ and other complex Salesforce® platform-based applications is what Prodly does best. That’s why Simplus has become the first Salesforce integration partner to join Prodly’s new partner program. By enabling faster and smoother Salesforce CPQ implementations, Prodly helps partners offer their customers a more cost-efficient service.

Leading Revenue Cloud Partner Integrates Prodly Deployment Solution

Simplus, a Platinum-level Salesforce integration partner based in Sandy, Utah, is the first organization to join the Prodly partner program. The agreement calls for Simplus to integrate Prodly’s relational data migration application into its implementation and post-implementation client handoff process.

David Belove, CEO of Prodly, said he’s excited and proud to kick off the new Prodly partner program with Simplus.

“We look forward to working with the entire Simplus team,” Belove said. “By using Prodly to implement Salesforce CPQ and Billing, Simplus will demonstrate the value of Prodly to hundreds of sophisticated Salesforce customers.”

Simplus’ decision to use Prodly demonstrates the importance of efficient, reliable relational data migration for complex native Salesforce applications like Salesforce CPQ, Billing, and Field Service Lightning.

Lance Evanson, EVP of Business Development at Simplus, said this partnership will help Simplus deliver a more complete, efficient, and higher-quality service to its clients.

“Prodly will enable us to reduce implementation cycles and use our valuable developer resources more efficiently,” Evanson said. “Equipping our clients with Prodly will help ensure they can successfully maintain their new applications after the handoff.”

Streamline Salesforce implementations

Streamlining Salesforce CPQ Reference Data Deployment

Prodly’s powerful data migration software will significantly reduce the time it takes Simplus to migrate Salesforce CPQ and Billing data. It will save hundreds of hours in project time. 

Simplus’ implementation teams will be able to easily migrate client product catalogs with thousands of products, price rules, and price rule entries. Prodly replaces the time-consuming and tedious manual migration process involved in using Data Loader and spreadsheets.

Unlike using Data Loader, Prodly’s data sets can be saved and reused over and over again. This will accelerate Simplus’ implementations. It will enable the Simplus Salesforce CPQ and Billing implementation teams to refine their best practices regarding relational data migration.

Simplus also plans to use and has helped validate Prodly’s new Salesforce CPQ data set templates. 

Gilles Muys is VP of Customer Solutions at Simplus and sits on the Prodly technical advisory panel. He was instrumental in advancing Prodly’s features set and CPQ template review process. This suite of 16 templates has been preconfigured to migrate Salesforce CPQ data. The result is that they eliminate hours of work to configure Prodly data sets for this popular application.

Implementing a Scalable Data Migration Process

BY streamlining Salesforce CPQ implementations, Prodly improves the scalability, reliability, and repeatability of the development and maintenance process for complex reference data.

Prodly is designed to support SIs and Salesforce customers with large development teams using its new centrally controlled deployment architecture. This feature supports data migration for multiple clients and multiple projects from a single instance of Prodly.

Templates simplify Salesforce CPQ data deployment

Templates Simplify Salesforce CPQ Data Migration

Using templates can significantly simplify the data migration process in Salesforce CPQ. In this blog, we’ll discuss the challenges associated with remapping lookup relationships. We’ll also explain how Prodly makes this process easier, faster, and more accurate. 

Why You Need Pre-Made Data Set Templates

There are 45 Salesforce CPQ reference data objects. It’s fiendishly difficult to deploy them from staging to production. The biggest challenge is remapping the lookup relationships among records in the destination org. Going back and forth with a data loader and spreadsheet is extremely tedious.

Prodly is purpose-built to solve this issue. It automatically reestablishes the source record relationships in the destination org. But there are still other challenges to quick and easy CPQ Salesforce data migration.

It’s time consuming to build a data set that involves dozens of Salesforce CPQ reference data objects, even for an expert. The first time around, it can take two weeks to perfect a Prodly data set for Salesforce CPQ reference data migration. 

Templates simplify Salesforce CPQ data deployment

This is time that most implementation consultants and in-house Salesforce CPQ admins would much rather spend on other things.

Another issue is establishing external IDs for every object to support updating records without creating duplicates. Salesforce CPQ doesn’t come with external IDs. That means implementation teams have to add them themselves.

So what to do? How about using our new pre-configured Prodly data set templates? They’re specifically designed for Salesforce CPQ. You’ll save a ton of time and avoid errors.

Salesforce CPQ Data Migration Templates From Prodly

Prodly has developed a suite of 16 data set templates that cover every aspect of Salesforce CPQ’s reference data—all 45 objects. This was with the help of Gilles Muys, former head of professional services at SteelBrick, now VP of Customer Solutions at Simplus. In addition, it was with demo data provided by the Salesforce CPQ team.

These templates are available at no charge to any Prodly user.

You can easily access the templates from GitHub. You can also download them as a zip file from the Prodly Resources page on our website.

The templates use the standard JSON file format, and you can import them into Prodly with a few clicks. Once you’ve installed them, you’ll see that all the object relationships are preconfigured. Additionally, composite external IDs are assigned to every object.

We’ve also developed the Prodly Salesforce CPQ Data Migration Guide. This is a comprehensive document that provides a detailed explanation of how the data sets are configured.

For more details about the templates, request a personalized demo.