Program Flow Transition

[erinkynett]

We have a Program for new customer onboarding with a Flow of four emails with various wait steps in between. We've recently done a content overhaul on these emails and created a new Program and Flow to start sending these out. Currently, we have an API set up that runs daily to push data into Marketo. What is the best way to start having the new customer data pushed to the new Program, and stop going to the old program, while also letting those customers in the middle of the Flow of the old Program finish going through each email?

[SanfordWhiteman]

What “data” is the remote service pushing to the Program exactly?

[erinkynett]

It is customer data. We are a financial institution. 

I don't think we need a solution anymore. We got a (complicated) answer from our Adobe rep, and we may end up using his suggestion if we need to, but to start, we're just going to put a bogus trigger in the "old" program so it will stop bringing in new people into the flow, but let the few who are in the middle of the flow continue through it until complete. 

[SanfordWhiteman]

@erinkynett please return to your thread and check replies.