Open to selected permanent, interim, and program-recovery rolesSeoul·EU–APAC
Sébastien TangENTERPRISE DELIVERY · GOVERNANCE · RECOVERY
Life sciences

Case study

7 Legacy Systems, Zero Data Loss

A global Salesforce migration with 100% of critical data moved and no data-loss incident

EngagementEnterprise Data MigrationDuration2021–22LocationParisYears2021–22

Sébastien Tang · Salesforce Enterprise Delivery Director. Leads complex Salesforce programs across delivery, recovery, vendor governance and the architecture decisions sponsors need to understand.

  • Administrator · Salesforce Certified
  • App Builder · Salesforce Certified
  • AI Associate · Salesforce Certified
  • Marketing Cloud AE · Salesforce Certified

The problem

A global migration had to consolidate critical data from seven disparate systems into a unified Salesforce environment without losing data.

What I did

The migration architecture used reusable templates, controlled source-to-target mappings, validation, and reconciliation checkpoints.

At a glance

Client
Sanofi
Sector
Life sciences
Engagement
2021–22
My role
Salesforce Data Architect, Global Migration
Salesforce clouds
Sales Cloud · Service Cloud
Outcome
0 data-loss incidents

Before / After

Before
  • Critical data distributed across seven source systems.
  • Migration mappings and execution needed a common control model.
2021–22
After
  • 100% of critical data moved into the unified Salesforce environment.
  • No data-loss incident recorded.
  • Migration error rate reduced by 85% through reusable templates.

Situation

Sanofi was consolidating critical data from seven disparate systems into a unified Salesforce environment. The engagement ran in 2021–22, with Sébastien Tang serving as Salesforce Data Architect for the global migration.

The public proof is deliberately narrow: seven source systems, 100% of critical data migrated, no data-loss incident, and an 85% reduction in migration errors through reusable templates.

Challenge

A migration can appear complete while still hiding missing records, duplicated data, or incorrect transformations. The control problem is therefore not only loading data. It is proving that the accepted target matches the approved source scope.

For this engagement, the required outcome was clear: move all critical data into the unified Salesforce environment without a data-loss incident.

Action

The migration architecture standardised source-to-target mappings, validation steps, reconciliation controls, exception handling, and reporting. Reusable templates reduced variation between migration activities and made errors easier to detect and correct.

The exact implementation details remain client-confidential. This public account therefore focuses on the verified control model and outcomes.

Result

One hundred percent of critical data was migrated from seven disparate systems into the unified Salesforce environment. No data-loss incident was recorded. Reusable templates reduced the migration error rate by 85%.

Those are the public outcomes of the engagement.

Reflection

The transferable lesson is control discipline: define the accepted source scope, standardise the mappings, reconcile evidence, and make exceptions visible before acceptance.

Zero data loss is an observed result here, not a universal promise for future migrations. Each program still needs explicit thresholds, evidence, ownership, and stop conditions.

Technologies used: Salesforce migration tooling, controlled mappings, reusable templates, validation and reconciliation controls

100%Critical data migrated
0Data-loss incidents
85%Migration error-rate reduction

Glossary

Source-to-target mapping
The controlled specification that identifies how each source field and value is transformed into the target Salesforce model.
Reconciliation control
A comparison between source and target evidence used to detect missing, duplicated, or incorrectly transformed data before acceptance.
Reusable migration template
A repeatable structure for mappings, checks, exceptions, and reporting that reduces avoidable variation between migration waves.

Frequently asked

  • Seven source systems were consolidated. One hundred percent of critical data was migrated with zero data-loss incidents.
  • Reusable templates standardised the migration work and reduced the error rate by 85%. Detailed client implementation data remains confidential.
  • No. It is the observed outcome of this engagement. Future migrations need their own reconciliation thresholds, exception process, evidence, and acceptance criteria.

Book the call

We'll know in 30 minutes
whether I can help.

No slides. No pitch deck. Bring the decision context and current artifacts, or describe the problem in your own words. I'll tell you whether I'm the right fit and what the next step costs — before you've finished your coffee.

  1. Response timing confirmed after review
  2. If I'm not the right fit, I'll point you at someone who is
  3. No follow-up emails unless you ask
Book a Discovery Call