Medical Devices · Dual Salesforce Org Consolidation + SAP Migration
OptovueOptovue
×
Cloud Nerd

Optovue Merges Two Salesforce Orgs and Migrates 90,000+ Records to SAP After Acquisition

When Optovue was acquired by Luneau Technology, two separate Salesforce organizations needed to become one — and three datasets totaling over 90,000 records needed to move to SAP. Cloud Nerd led the integration and migration across sixteen weeks.

Engagement at a glance

Industry
Healthcare
Duration
16 weeks
Services
Architecture & Design · Build & Implement · Integrations · Migration & Modernization
Stack
SalesforceSalesforceSAP FSM/ERPSAP FSM/ERP
2 orgs

Salesforce organizations integrated into a unified customer 360

90,000+

Records migrated to SAP across three data sets

6 objects

Synced bidirectionally between Optovue and Luneau Salesforce orgs

16 weeks

Discovery through production deployment

The challenge

Optovue's acquisition by Luneau Technology left the combined company with two separate Salesforce organizations — each holding customer data the other couldn't see. Sales reps at both companies had an incomplete view of shared customers. Simultaneously, Optovue's Install Base (15,461 records from Oracle), Service Cases (59,301 records), and Clinical Applications (15,831 records) all needed to be harmonized and migrated to Luneau's SAP FSM/ERP system.

The approach

Cloud Nerd architected and executed two parallel workstreams: a bidirectional Salesforce-to-Salesforce integration using a middleware platform to sync Leads, Accounts, Contacts, Opportunities, Products, and Price Books between both orgs; and a structured data migration of three datasets from Salesforce and Oracle into SAP, including full data harmonization — matching, deduplication, formatting standardization, merging, and transformation — before import.

The outcome

Sales reps at both Optovue and Luneau now have a complete customer 360 view in their respective Salesforce orgs, with data staying in sync across the combined company. The SAP migration gave Luneau's operations team clean, harmonized Install Base, Service Case, and Clinical Application data in their ERP system for the first time.

The problem

What was actually broken

01

Two Salesforce orgs with no shared data

Optovue and Luneau maintained completely separate Salesforce instances. After the acquisition, reps at each company couldn't see opportunities, accounts, or contacts from the other side — creating blind spots in joint customer conversations and sales forecasting.

02

90,000+ records requiring harmonization before SAP migration

Three datasets — 59,301 Service Cases, 15,831 Clinical Applications, and 15,461 Oracle Install Base records — each had inconsistencies, duplicates, formatting issues, and field mapping gaps that had to be resolved before they could be safely imported into SAP.

03

Oracle-to-SAP migration with no direct path

The Install Base lived in Oracle with a completely different data model from SAP. Cloud Nerd needed to design and build a custom ETL migration that could handle the structural transformation at scale.

How we did it

The work, phase by phase

  1. 01
    Weeks 1–5

    Discovery & Integration Platform Selection

    Cloud Nerd ran structured discovery with both Optovue and Luneau teams, defined the data mapping dictionary, designed the bidirectional integration architecture, and led the selection of an integration middleware platform.

    • Data mapping dictionary for Leads, Accounts, Contacts, Opportunities, Opportunity Line Items, Products, and Price Books
    • Data synchronization schedule and transformation rules defined
    • Integration middleware platform selected and procured
    • Migration schema models for Service Cases, Clinical Applications, and Install Base
    • ETL solution design for Oracle-to-SAP migration
  2. 02
    Weeks 4–12

    Integration Build & Data Harmonization

    Cloud Nerd built the bidirectional Salesforce-to-Salesforce integration and ran full data harmonization across all three SAP migration datasets.

    • Bidirectional org sync live: changes in either Salesforce org propagate to the other
    • Data harmonization completed for Service Cases (59,301 records): matching, deduplication, formatting, and transformation
    • Data harmonization completed for Clinical Applications (15,831 records)
    • Data harmonization completed for Oracle Install Base (15,461 records)
    • ETL pipeline built for Oracle-to-SAP data movement
  3. 03
    Weeks 12–16

    SAP Migration, QA & Deployment

    Cloud Nerd executed the production data migration to SAP, ran full QA testing on both the integration and migration outputs, and completed the production deployment.

    • 59,301 Service Cases migrated to SAP
    • 15,831 Clinical Applications migrated to SAP
    • 15,461 Install Base records migrated from Oracle to SAP
    • Regression and end-to-end UAT completed across both workstreams
    • Production go-live with both integration and migration verified
The results

What changed for Optovue

90,593

Records harmonized and migrated to SAP across three datasets

Customer 360

Full shared account view for reps at both Optovue and Luneau

Bidirectional

Real-time sync between two Salesforce orgs on a defined schedule

16 weeks

Full integration and migration from discovery to production

What's next

Optovue and Luneau are evaluating full Salesforce org consolidation — merging the two instances into a single unified Salesforce organization as the combined company's go-to-market motion continues to integrate.

Technologies in this engagement

SalesforceSalesforce
SAP FSM/ERPSAP FSM/ERP

Ready to do this?

What would we build
at your company?

Book a 30-minute strategy call. We'll walk through exactly what we'd do on your stack — no commitment, no pitch deck, just specifics.

Book a Strategy Call