SALESFORCE CLONE, SPLIT, MERGE

The Press

Salesforce Org Clone, Split, Merge and Legacy Data Migration

Salesforce customers often need to consolidate their data into one Salesforce org because of mergers or organizational changes. They also need to split data into separate orgs due to corporate divestiture. Often the source data is from other CRM’s, which involves transforming data fields and the data model itself. Sesame Software’s professional services team uses Relational Junction to split or merge data based on business rules and transformations that can be specified in spreadsheet format. This spreadsheet is used directly by the process to generate all the transformations without coding.

Use Cases

Corp. merger, acquisition, divestiture, realignment of business units, or testing needs, data in one or more Salesforce orgs

CLONE

    • One organization splits into two or more business units or companies, but both want all the data.
    • Frequent Salesforce sandbox refreshes are needed by developers for testing, possibly with a subset of the original data.

SPLIT

    • One organization splits into two or more companies or business units, with each receiving only their portion of the data.
    • A global organization wishes to separate business units into separate systems, but also create a combined org with all the data.

LEGACY DATA MIGRATION

    • Migrating data from legacy CRM’s or other data sources requires an understanding of the relationships, transformations, and data models of both systems. Usually both systems are required to be in sync for a period of time, a “trickle feed” process where new or changed records from the source system are fed into Salesforce over a period of time until the old system is shut down, or in some cases longer.

MERGE

    • Corporate acquisition of another company who uses Salesforce, or another CRM.
    • An Enterprise decides to merge all its business units into one org, and keep a combined structure and data.

Conversion Window

Relational Junction is natively designed for both of the following scenarios:

PHASED APPROACH, WITH BOTH SYSTEMS BEING USED WHILE THE MIGRATION HAPPENS

    • Used when we can’t meet the conversion window due to volume constraints.
    • Used when the business doesn’t have a single cutoff date.
    • Don’t have the luxury of shutting down Salesforce usage for a weekend.
    • Both orgs are being synced for a period of time, due to needs of the business to maintain both systems until a business-driven cutoff date.

ONE TIME MIGRATION WITH PLANNED OUTAGE OF SALESFORCE.COM USAGE

    • Requires weekend shutdown with no Salesforce updates.
    • Duration of shutdown depends on data volumes.
    • Migration must be tested using a Sandbox, often multiple times.
    • This is the easy way, where you only convert the data once, and have the luxury of a planned outage.

Patented Handling of Data Model Relationships

MANAGING PARENT-CHILD AND RECURSIVE RELATIONSHIPS

When creating new data in Salesforce, particular care must be taken to maintain relationships between parent and child records, such as Account and Contact. Additionally, recursive relationships must be maintained at any level, such as as parent Accounts or Contact Reports-To hierarchy. This requires multiple passes, and complex logic.

Relational Junction implements fully automated logic to handle all relationships without any coding. This is also why Relational Junction makes data recovery so easy, no matter how complex the data model.

Find out how Relational Junction for Salesforce can help your business!

The Press