Does DTM to Launch Migration Tool not copy over Inactive DTM Rules? | Community
Skip to main content
Level 2
February 25, 2020
Solved

Does DTM to Launch Migration Tool not copy over Inactive DTM Rules?

  • February 25, 2020
  • 4 replies
  • 6236 views

We have used the DTM to Launch property migration button to get several of our properties migrated over from DTM to Launch. Upon closer examination of the Launch property today, it looks like rules that were inactive in DTM were not copied over to the newly created Launch property. Has this happened to anyone else, or is this something that is unique to our company? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sebastiane_Edberg_

Yes the migration only takes active rules and elements

4 replies

Haran_Huang
Level 4
February 26, 2020
Yes, just migrate the production environment.
Sebastiane_Edberg_
Community Advisor
Sebastiane_Edberg_Community AdvisorAccepted solution
Community Advisor
February 26, 2020

Yes the migration only takes active rules and elements

Sebastiane_Edberg_
Community Advisor
Community Advisor
February 27, 2020
Be wary of one thing though, you remember that nice migration feature which lets you keep the DTM embed code and still reference launch library? messed things up for us as we had choose not to have that but it still kicked in when we published launch library all the way to production, got a little bit messy and still no answer from Adobe how it can happen. Looking at the production environment in Launch it does not indicate that it is linked but it happens anyway.
benAllenAuthor
Level 2
February 27, 2020

@sebastiane_edberg_, so what happened to your implementations? Did the Old DTM codes overwrite your new Launch embed codes or were the Launch embed codes correct but you were still getting served your DTM production libraries? I chose not to link our production Launch code to our production DTM code too so I am interested in hearing more about this. Have you tried disabling your old DTM property now that you have migrated over to Launch? This might solve your issue by disallowing the Launch embed codes from accessing the old DTM libraries.