Tag Archives: salesforce cpq

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.

Scalable data migration with Prodly

Data Migration in Salesforce Is Scalable With Prodly

Data migration in Salesforce can be more scalable, repeatable, and reliable. And we’re going to make it happen.

That was the challenge the team at Prodly set itself. And with its Fall 2017 release, Prodly’s introducing new features, core enhancements, and upgrades. It has now evolved from a single-user tool for migrating relational data to a robust platform for complex data migration.

How to Make Data Migration More Scalable

Upon its release in 2015, Prodly instantly became the most powerful tool for automatically migrating relational data between Salesforce organizations. Fast, easy, and efficient, it cut data migration time from as much as 12 hours to as little as 30 minutes.

At the heart of Prodly’s success was its ability to maintain complex parent-child relationships during the migration process. This eliminated the need to perform extra time- and money-wasting steps that were repetitive and prone to human error.

Now, with the Fall ’17 Release, Prodly has elevated itself to new heights. It’s become the premier platform for managing Salesforce data migration for complex applications such as Salesforce CPQ and FinancialForce.

Already fast, secure, and efficient, Prodly’s new features and upgrades support a more scalable, reliable, and repeatable data migration process. This makes the platform a natural fit for high-volume systems integrators and Salesforce users with large development teams.

Scalable data migration with Prodly

Centrally-Controlled Deployment Architecture

With Prodly’s new centrally-controlled deployment, you only have to install it in a single central Salesforce organization. From the central org, you control all your deployments. You can connect to all your organizations and using any of them as a source or destination.

The new streamlined architecture saves time and effort, eliminating the need to perform repeated installs. For Salesforce customers with large development teams and for SIs working with multiple source orgs, time saved translates into money saved. This allows teams to reallocate those work hours to other more important tasks.

Multiple Destination Deployment

Prodly’s ability to support multi-org projects isn’t limited to its centrally-controlled deployment architecture. With multiple destination deployment, you can now push data sets to as many as five destinations at once.

This new feature should prove particularly attractive to high-volume SIs and Salesforce users with many sandboxes. With just one click, you can deploy the same data set to multiple sandboxes. This feature eliminates the need to repeatedly perform and validate time-consuming deployments to every desired destination organization.

Data Set Templates

One of the most exciting new Prodly features is the ability to create data set templates. You can export a data set from one Prodly instance as a template file in JSON format. After that, you can  import it for use in another Prodly instance.

But that’s not all. Prodly has made things even easier to make users t even more self-sufficient. It provides updated, ready-to-use Salesforce CPQ data set templates are now available to download.

Another benefit of creating templates in Prodly is that you can back up data sets for better version control. That’s an incredibly useful feature in any large Salesforce development environment.

Other New Prodly Features

A series of other upgrades and updates will also enrich the user experience and simplify the implementation of popular Salesforce applications:

  • Field value scrambling: Scramble field values like social security numbers or email addresses in destination organizations for added privacy and security.
  • Empty field values: Set deployed fields to an empty value in the destination organization. This clears out fields to align with business requirements.
  • Fixed field values: Set deployed fields to a fixed value in the destination organization to align with business requirements.
    Lightning components for data set import and deployment. Start a deployment or import a data set template from any page in Salesforce Lightning Experience.
  • Permission Sets: Assign admin and user permission sets to segregate the activities different employees can perform. Using standard Salesforce platform sharing settings, you can also implement additional security to isolate users working on specific clients and projects.
  • Set audit fields: Set record system fields using the Salesforce Create Audit Fields option.

Prodly’s not stopping here in its mission to make data migration more scalable. Keep an eye out for more useful, time-saving features in future releases.

Simplify Salesforce data migration

Simplifying Salesforce CPQ Implementations for Coastal Cloud

Coastal Cloud leverages Prodly to facilitate faster, more accurate Salesforce CPQ implementations.

Salesforce CPQ Implementations Are Smoother With Prodly

Coastal Cloud is a Salesforce™ Platinum Partner based in Florida, with additional development centers in Kentucky and Colorado. They help clients leverage Salesforce Revenue Cloud (Salesforce CPQ and Billing) to improve business results and deliver a superior customer experience.

Q2C implementations can be a time-consuming process due to the complexities of relational data migration. Coastal Cloud has overcome this challenge by employing Prodly.

This Q&A with Mike Ackerman of Coastal Cloud discusses how his team uses Prodly to enable efficient Salesforce CPQ implementations.

Simplify Salesforce data migration

Q: Mike, what is your role at Coastal Cloud?

I’m a senior technical architect at Coastal Cloud. I help our client implementation teams during the design, build, and deployment phases. I promote best practices and best-in-class tools so our consulting teams can deliver projects consistently and efficiently.

Q: Can you describe Coastal Cloud’s experience with Salesforce CPQ and Billing implementations?

We’re a leading implementation partner of Salesforce Revenue Cloud, which includes Salesforce CPQ and Salesforce Billing. We’ve implemented some of the largest and most complex quote-to-cash deployments to date.

Coastal Cloud is on a shortlist of partners with deep experience in both CPQ and Billing. We’re a long-standing partner. We worked with SteelBrick, which was founded by Prodly’s CEO, before it was acquired by Salesforce and became Salesforce CPQ. We’re happy to say that relationship continues today.

We’ve performed many Salesforce CPQ and Billing deployments with complex configurations of products, pricing, availability, discounting, billing, and revenue recognition rules.

Our quote-to-cash projects range in complexity. We’ve completed simple Salesforce CPQ implementations for midsize companies and highly complex implementations for large enterprises. With quote-to-cash playing a central business role, we often integrate with ERP and other systems.

Q: Why is quote-to-cash, and CPQ in particular, so challenging from a relational data migration perspective?

The real power of Salesforce CPQ is the flexibility and configurability. You need the ability to make product catalog reference data changes quickly and easily to leverage that power.

However, there’s a complex reference model working behind the scenes to enable this configurability in Salesforce CPQ. Implementation teams need to treat this reference data as another important artifact to be appropriately managed across environments.

When it comes to disciplined configuration management, you need to treat reference data as a first-class citizen. This is alongside the programmatic and declarative deliverables necessary to build and deliver the project.

Q: Why is relational data migration such a challenge?

Before we discovered Prodly, our teams executed a very labor-intensive process. It involved exporting configuration data changes to spreadsheets and meticulously loading them back into the target environments.

Salesforce’s internal IDs and lookup relationships are very complicated. So that load process had to account for the re-keying of relationship data. We needed to carefully load the parent and child rows in the correct order. Then we have to re-key the child rows to point to the newly imported parent.

This is a concern with related objects, as well as with rows within the same object that have a recursive relationship. You need to ensure that you’re loading the rows within the same object in the right order. Plus, you need to re-key those child rows before you can load them.

When you deliver changes to an existing target of reference objects, you identify each row with a unique external key. That way, you know if a row is being updated, inserted or deleted.

As you can imagine, using export spreadsheets with Data Loader can be a very labor-intensive and error-prone process.

After we discovered Prodly, this became a much more automated process. It saves us significant effort and reduces the risk of error.

Q: How long did it take to migrate reference data without Prodly?

Many factors impact the complexity of the Salesforce CPQ and Salesforce Billing model. Think of how many products are in the catalog, as well as the number of options and features you have. In addition, consider the complexity of the pricing and discounting rules.

All these factors influence the migration effort. However, it can easily take a full day to do one load without effective tools. This isn’t a scalable process when you’re following an agile development model.

Q: How do you integrate Prodly into your Salesforce CPQ implementation process?

In an agile development environment with two-week sprints, you want to set up and shut down feature development environments frequently.

To make your developers productive, provide them a full copy of the product catalog from which to develop and test. And you need to reduce that full-day migration process to execute refreshes reliably and frequently.

Let’s say we have three developers working on a two-week sprint. We start the sprint by setting up three empty DevPro orgs . Then we use Prodly to instantly populate these empty orgs with current product catalog reference data. Later, we’ll migrate that reference data to a fourth environment to support testing activities.

We also use Prodly for quick, ongoing deliveries of incremental data changes for bug fixes. When a fix is ready for production, we save time and reduce risk by delivering the final reference data using Prodly.

Note that we reduce our users’ outage window significantly by using Prodly during the production migration.

Q: How do you avoid duplicates when you migrate relational data?

You’ve got to ensure you have a unique surrogate identifying key on each of the rows of the product reference objects.

Prodly uses this key to identify whether it’s an insert, update, or delete action when copying the data. Hopefully, a surrogate key exists in your data set already, but a lot of times we find one does not.

For instance, you might assume the product SKU is surrogate, but in reality there may be business meaning in that SKU. Perhaps those first two letters of the SKU indicate the line of business.

Perhaps the business team decides somewhere down the line that they want to change that SKU during a rebranding effort. Where you thought something was a surrogate unique identifier, it may in fact change in the future. That could break your deployment process.

Ideally, you want to start the project by identifying truly unique surrogate IDs for each row. You want the developers to set a surrogate ID once—and know it is never going to change.

IDs should have no business meaning and must reliably identify the uniqueness of a row as it moves across environments.

As Salesforce developers know, we can’t use the Salesforce ID for a surrogate key. The ID is not updatable and it changes as it moves from org to org. Surrogate IDs are an important success factor in making the reference data management process reliable.

Q: How exactly do you configure Prodly data sets to migrate CPQ reference data?

Today, this is part of the startup steps for getting a Salesforce CPQ implementation project up and running. We install Prodly in the client’s org. Then we the data set or template for the objects we’re going to ask Prodly to move back and forth.

The data set represents the configuration, or instructions, on how the data will be moved. We define this initially in production to prepare for the copy of data from production to our development and test orgs.

When you’ve made changes in the development org, it becomes the new source. Those changes can be copied to test and later to production. To re-use the data set configuration we already defined in production, we copy it to the development org. That way, it can also facilitate that org’s new role as being the source for changes.

Currently, Prodly must be installed in any org that acts as a source for copying data. We can also use Prodly to push its own data set configurations to and from various source orgs. That way, we don’t need to re-define the data set from scratch. We’re essentially creating our own template.

With Prodly’s centralized deployment architecture, pushing data sets and installing Prodly in the various source orgs will no longer be necessary. Instead, we’ll be able to manage deployments from a central org. This will be another big time saver.

The centralized deployment console can potentially offer smaller clients a shared reference data management service based on Prodly.

Q: How do you hand off the reference data update process to a client once you finish your Salesforce CPQ implementation?

Our standard methods and tools now include the use of Prodly for managing complex reference data migrations.

During our discovery phase, we identify if these challenges are present. Our teams identify this risk early and ensure the project is scoped to include the appropriate tools to mitigate this risk. This helps to ensure our clients and delivery teams are set up for success.

Prodly is a key part of our risk mitigation tool set.

Ideally, we want our clients to procure their own Prodly licenses. That way, once we’ve successfully delivered our project, the client’s Salesforce support team can continue to smoothly execute the process.

We ensure the process is well documented and train the client’s administrators on how to use the tools. We have a very robust configuration and release management process that’s well documented and repeatable.

Some clients opt to engage us for long-term Salesforce support. In those cases, which we continue to leverage Prodly for highly efficient reference data management.

Q: Any final thoughts?

Using Prodly, we’ve been able to dramatically improve the efficiency and quality of managing our Salesforce quote-to-cash data. We’ve taken a day-long reference data process and now execute it reliably in mere minutes. Prodly has drastically improved the way we operate and increased the ROI for our Salesforce quote-to-cash clients.

Do these Salesforce CPQ data migration challenges sound familiar to you? 

Schedule a free demo now to see how Prodly can help !