Guidance Needed: Migrating from Tealium to Adobe SDKs with Two Different Org IDs (AA v5 + AEP) | Community
Skip to main content
Level 4
June 15, 2026
Question

Guidance Needed: Migrating from Tealium to Adobe SDKs with Two Different Org IDs (AA v5 + AEP)

  • June 15, 2026
  • 1 reply
  • 0 views

Body:

Hi everyone, We’re in the middle of migrating our mobile apps from Tealium to Adobe’s mobile SDKs, and we’ve run into a challenge with Org IDs that I’m hoping to get some guidance on.

Current Setup

We currently have two different Adobe Org IDs in use:

  1. Adobe Analytics v5 SDK (Legacy)

    • Data flows directly into Adobe Analytics

    • Uses Org ID #1

  2. AEP Mobile SDK (New)

    • Data flows into Adobe Experience Platform

    • Uses Org ID #2

The Problem

During the migration, we need both data streams to continue:

  • Data must still flow into Adobe Analytics (Org ID #1)

  • Data must also flow into AEP (Org ID #2)

However, since the AEP Mobile SDK is tied to a single Org ID, we’re unsure how to architect the migration so that both systems receive the same events.

Questions

  1. Is it possible to send events to AEP using MobileCore.trackAction / sendEvent, and then use Event Forwarding to route those events into Adobe Analytics (Org ID #1)?

  2. Is this the recommended approach for customers who need to support two Org IDs during a transition period?

  3. Are there any limitations or known issues with forwarding AEP events to Adobe Analytics via Edge + Event Forwarding?

  4. Is there any alternative best‑practice approach for dual‑Org setups during migration?

We need to maintain data continuity in both systems until the migration is fully complete, so any guidance or architectural recommendations would be greatly appreciated.

Thanks in advance for your help.

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
June 15, 2026

Hi ​@jaishal,

I haven’t dealt with this scenario, but it sounds extra tricky…

 

Have you talked to your account reps to see if Adobe has thoughts on how to handle this? I am surprised no one flagged this as an issue when the decision was made to set up a new org…

If you can’t get help from your account reps, you could also try reaching out to client care… 

 

Event forwarding sounds like a logical solution.. though expensive… but you may not have many other options…. I wonder if you could also set up a custom solution using the Ingestion API to send data to your AA implementation (without relying on the SDK)? I feel that no matter which solution you choose, you will basically be re-doing your Adobe Analytics (Org 1) implementation and it will require a full regression test… 

 

Good Luck!