Migrate your legacy BPM system to Salesforce


If your organization is still running legacy BPM systems and you have implemented Salesforce, you need to look at migrating them to Salesforce.

Using Work-Relay, we have migrated legacy IBM Lombardi and IBM Lotus Notes systems to Salesforce for Fortune 500 companies. We have also migrated other legacy BPM systems like PMG and newer tools that are not 100% native Salesforce like Workfront and Smartsheet.

The cost savings can be enormous. For example, a company that had been running IBM Lombardi for the last 20 years was able to de-commission 44 servers, plus the software maintenance fees and support.

The ability of Work-Relay to replace these products is a good indication of how powerful Work-Relay is.

1. A single database

Native applications share a single database with Salesforce.com. So there are no data synchronization, connection issues or data loss between databases. Having a single data store also helps increase the speed of accessing data, generating reports or generally mining the data because there are no round-trip transactions needed with the data.

2. Administration

Your Salesforce administrator already has the knowledge and skillset of the platform, and is capable of running any additional native applications your company decides to implement.

3. Updates and upgrades

Updates and upgrades are made easier, because they can be done in one place and made instantly available through all native apps.

4. integration

Because the native apps are all built on the same platform, it’s easy to integrate them with each other.

5. Physical security

Because you do not have to connect third party applications using APIs, your data resides in the Salesforce database and never leaves. It is not sent or stored on an outside server nor does data enter from external servers, which may be the case with non-native apps.

6. Security policies

Native apps use the same Salesforce security model which eliminates the need to manage multiple security policies and procedures across the corporate systems. With a non-native app, these rules and settings may not be applied, and as a result, data could be vulnerable.

7. Availability

Since native apps reside 100% within Salesforce they will always be up and running when Salesforce is running.

8. Performance

Native apps have the exact same guaranteed performance as Salesforce apps.

9. Trust

Native apps follow trust.salesforce.com policies and best practices.

10. Accessibility

All data records are available for your Salesforce Reports and Dashboards.

11. implementation

A native app can be installed and running in minutes.

12. Adoption

Users are already familiar with how Salesforce works, significantly lower cost of adoption.

13. Infrastructure

Native apps are delivered on the Salesforce infrastructure, which your IT group has already reviewed and approved.

14. Chatter

Native apps are typically fully integrated with Chatter, while other vendor solutions are likely to have their own collaboration and communication mediums.

15. Customization

Native apps can be customized by non-technical users by adding new fields, workflow rules, etc. Developers can write custom code in an environment and with a tool set they are already familiar with.

16. Cost

You are already paying a license fee for a lot of functionality that will be duplicated in the external application – infrastructure, security, database, content manager, etc.

17. Salesforce API

Native Salesforce apps work entirely within the Salesforce environment and don’t have to pass data through the Salesforce API. Applications that integrate with Salesforce have to use the API to transfer data back and forth, and can result in additional charges.

18. Commitment

Companies with fully native Salesforce applications are clearly committed to Salesforce for the long term. This may not be so for external service providers.


There are instances where a company will create a Salesforce app add-on to their core application, or use data that is stored outside Salesforce. These are non-native applications.

So if the answer to these questions is not “Salesforce”, it is not a native app:

  1. Where is the core application hosted?

  2. Where is all the data stored?


Migrating your legacy BPM system to a 100% native app will save you time, money, and effort.

Since you have already invested in Salesforce, it only makes sense to leverage the platform as much as possible!


Download Work-Relay Features eBook

Leave a Reply