Customer:

Financial Solutions & Payment Services Provider

 

In Partnership With:

Configero-Logo

 

Industry:

Financial Services

 

Services: 
Agile Development | Payment Gateway Integration

Technologies:

Salesforce | Python | Heroku | Amazon Web Services

 

Tools:
Git | Gearset


Platform:
Force.com

 

Simplifying Acquisition Onboarding for a Fintech Major

As part of a recent acquisition, the customer had acquired managed Salesforce packages. We migrated these to unmanaged packages, helping the customer achieve greater efficiencies and easily onboard new acquisitions.


 

About the customer

The customer is a payment technology and processing solution provider. Their offerings are comprised of a full suite of payment technology products, including debit and credit card processing, Automated Clearing House (ACH) processing, instant funding, and more. The company has appeared on the Inc. 5000 list of fastest growing US companies for eight years in a row.

10,000+

merchant locations

14

years in operation

5+  

industries served

 

Business challenge

The customer, a payment gateway provider, tracks and stores information about transactions between end-users and banks, providing end-to-end reports to the bank. They used the Salesforce system as their CRM, using various natively designed Salesforce features to collect customer-related databases and records and share it on different servers.

The customer had recently acquired some of their vendors, who were earlier providing their services for a fixed fee. Acquiring these vendors allowed them to save on these costs. As part of the onboarding of these newly acquired companies, the six managed packages they were using on Salesforce needed to be converted to unmanaged packages and integrated into the customer’s Salesforce CRM. These unmanaged packages would provide developers with the basic building blocks for applications and allow them to edit components. All dependencies that existed in these packages needed to be resolved without losing any data and setup configuration.


 

Solution

Technologies used for migrating Salesforce packages


Middleware Cloud Server Backend SF Devops Tool
Heroku
Amazon-Web-Services
Python
Gearset

To integrate these different systems, we used Heroku as the middleware, and Python as the backend technology to read and parse the metadata.

Python’s ability to read compressed files and folders, extract files and find references inside them helped us find dependencies and resolve and replace these with unmanaged references.

We created new compressed files with collections of modified content, and pushed these back into the system using Gearset. Heroku acted as the central node with connections to different systems to fetch data.

These were the steps involved in dependency management:

01. Identification
02. Replacement
03. Execution
04. Deployment
Identifying dependencies and references of managed package components across the entire Salesforce organization Using Python as the backend technology to find dependencies and replace them with unmanaged entities Executing Python scripts in the entire Salesforce code base with 60+ Salesforce components Deploying the data with unmanaged entities back to the Salesforce organization using Gearset


 

Results

Cost Savings Realized

Cost Savings Realized

By integrating their systems, the customer was able to save on the fee they were paying to their vendors and achieve greater efficiency.

Reduced Dependencies

Reduced Dependencies

They were also able to reduce their dependencies on third-party vendors, gaining the ability to customize the system as needed.

 

Simplified Onboarding

Simplified Onboarding

Seamless integration between new and existing systems made it easier to onboard future acquisitions and provide better support to them.

 

 

 

 

Quote
“Very happy with the team. They are all hard working and competent. I also like that they were able to work flexible hours for us.”
Alex Sartogo
Alex Sartogo
Vice President Technology

 

Project Highlights

Block Tabs

Salesforce Data Migration

These were some of the parameters taken into consideration during the migration:

 

  • User Mapping: Ensuring that record ownership is set up correctly in the new system
  • Security: Ensuring existing profiles and organization-wide defaults are properly set up in the new environment
  • Space: Ensuring that the current Salesforce environment is large enough to handle the additional data being migrated into it
  • Backups: Ensuring that the old data environment is backed up before initiating a new Salesforce data migration

 

Onboarding

This involved the identification of order of insertion of records into the Salesforce system while checking the consistency of naming parameters.

 

Payment Gateway Integration

Since the customer was a payment gateway company, a large amount of customer data needed to be loaded in Salesforce. Heroku was used to load bulk data using CSV files.