Skip to main content

I have been spending a lot of time lately working through Data Cloud deployments across Sandbox → UAT → Production, especially when the underlying source systems (in my case: Redshift Dev vs Redshift Prod) aren’t identical in access patterns.

One thing that surprised me early on was how tightly Data Streams and DLO/DMOs stay tied to the connector they’re created with. If a Data Stream is built on RedshiftDEV and moved through a Data Kit, it still points to the DEV connector unless you manually adjust it.

A simple best practice that has helped me a lot:

👉 Keep connector names consistent across all environments (even if they point to different databases).

Migration becomes smoother, cleaner, and avoids those “why is this not fetching rows?” moments.

Curious how others are handling connector mapping or remapping during deployments.

Do you standardize connector names?

Or recreate Data Streams manually in each environment instead of migrating them?

Would love to hear what’s worked for your teams.

#Analytics #AppExchange
1 comment
  1. Nov 17, 2025, 6:55 AM

    Hi Mam, 

    I don't have much knowledge in data cloud , but while going through Agent force topics , i came across some of the topics related to data cloud . 

    with the limited knowledge i have what i feel is

     '

    if maintain/Standardize connector names across all environments , it would be good for migration tasks/post deployment activities and also good for automation'. 

    Regards, 

    Srinivasa

0/9000