SFDC – IT Services – Data Migration using Relational Junction – Success Story

Client Overview

Client is the USA based IT service provider of enterprise non-profit constituent relationship management (CRM) solutions. The client is focused on providing services to leading global nonprofits, media houses and higher educational institutions.

The client also implements and supports front-end solution for large universities, helping to maximize revenue and reduce costs by effectively automating functions of recruiting, retaining, connecting and engaging prospective students and alumni.

Business Challenge

Data Migration is a complex process, requiring a robust methodology and structured framework.

The business need was to migrate all the data from a live legacy CRM database to Salesforce objects, map and validate this data in the production environment. The key challenges were –

  • Understanding schema of legacy CRM system and mapping it to SFDC objects

  • Figuring out steps to migrate millions of records (large volume) in quick time and ensure high data quality (no duplicates, no data gaps or lost records, object relationship is maintained)

Technical Requirements

  • Apex

  • SQL Script

  • Relational Junction (RJ) data migration tool

Solution Strategy

  • Eternus Solutions was engaged with the client in the capacity of an Offshore-based Delivery Center, collaboratively taking care of the data migration from live legacy CRM database to Salesforce.

  • Manual Data Migration using SFDC Data Loader is a time-consuming activity especially for very large data volumes. To overcome the time-consuming manual process, Eternus Solutions proposed and implemented Relational Junction (RJ) tool as the data migration tool.

  • RJ helped to reduce time and efforts required for the data migration by helping automate the mapping and scripting process between the two system schemas.

  • The required business data was fetched by creating views and scripts in RJ, building transformation rules, conditions and pushing the output to RJ’s replication tables. RJ commands were used to keep data in sync with the legacy CRM database.

Figure 1 – Data Migration Architecture with Salesforce.com

Development Methodology

  • Loading of data in the Developer Sandbox

  • SRS and design documents to start building any new components

  • Design and development of workflows for various processes wherever required

  • Design and development of scripts for various jobs and objects

  • Development of scripts using best practices and Database standards

  • Data Tool Configuration using standard editor

Solution Components

  • Customization of existing Standard objects

  • Creation of new objects

  • Triggers/workflows, classes to manage the business work flow

  • Data analytics using business dashboards and reports

  • Creating new views, stored procedures and functions

Share This Case Study