DTM Plans for a Sunset

Avatar

Avatar

thebenrobb

Employee

Avatar

thebenrobb

Employee

thebenrobb
Employee

05-10-2018

maui_sunset.jpeg

Update: The DTM Sunset Milestone dates outlined below have all been shifted back 1–2 weeks to accommodate release cycles and company events. Individual dates may be shifted again as they approach, but we promise they won’t be sooner than what’s below.

--

March 2020 Update: We’ve heard from a number of customers that the COVID-19 situation is disrupting the priority of their tagging projects, resources, and timelines. To aid with this situation, the target dates for Milestone 2 and 3 below have both been pushed out by 3 months. We’ll continue to listen to feedback from customers and may further extend the dates.

--

July 2020 Update: We continue to hear from customers who are concerned about the impact that the COVID-19 pandemic is having on their migration timelines. We have resource, maintenance, and cost constraints that make it infeasible to push back Milestone 3 (the final EOL), but we have decided to shrink the read-only period from 6 months down to 2 months. This means that while the final EOL timeline is not changing — it is still April of 2021 — you’ll be able to continue to make changes to your DTM properties until February of 2021. The official dates below reflect the latest changes.

--

Last November (2017), we released Launch to Production and started giving access to customers who requested it through a random selection process. At the same time, we started giving new Experience Cloud customers access to Launch instead of DTM.

Earlier this year at the US Summit (March 2018), we ended the random selection process and made Launch available to all Experience Cloud customers. Since that time, we've had close to 1,000 different customers log in and create properties in Launch. Half of them have published to their Production environment - and are using it live, we assume 😃

This summer (July 2018), we released an upgrade process in DTM to provide a self-service, automated way to move your DTM properties into Launch. You can read more about this in the blog post and in the product docs.

We continue to add new features to Launch. In the coming months, you’ll see things that were never possible in DTM like private extensions and mobile properties for managing SDKs in your native mobile applications. You’ll also see better versions of things that DTM already has like comparing revisions and bulk copy.

Maintaining both DTM and Launch in perpetuity was never the plan and is not a sustainable path forward. Looking ahead, DTM will be in maintenance mode. We’ll keep it up-to-date with security fixes, critical bug fixes, and Experience Cloud changes.  We will not be doing any feature development.

Over the next few years, we will be introducing progressive restrictions on what you can do within DTM. We want to be transparent with those plans so that you can plan your upgrade path accordingly.

Timeline

Milestone 1: 2019–07-09

Starting in July of next year, DTM will no longer allow the creation of new properties. This will have no impact on existing properties.

Status: Complete

Milestone 2: 2021-02-16

In February of 2021, DTM properties will enter a Read-only mode. You will not be able to create or edit tools, rules, or data elements. You will no longer be able to publish to DTM environments. This will have no impact on previously published libraries.

Milestone 3: 2021-04-13

In April of 2021, DTM will go dark. Servers will be decommissioned, documentation will go offline, and communities will be removed. This will have no impact on previously published libraries.

We hope that by letting you know about these things in advance, you'll be able to make and execute your plans to upgrade to Launch without interruption to your business. You'll be joining your Experience Cloud peers who are taking advantage of Launch's open ecosystem, asynchronous deployments, new rule builder, and the APIs.

Happy Tagging 😃

This post first appeared on the Launch blog.  You can follow us there.

4 Comments

Avatar

Avatar

sophiebegley

Avatar

sophiebegley

sophiebegley

30-03-2020

As much as this is appreciated, the shifting of this timeline actually has minmal-to-zero impact to our project timelines. Our business operates a code-freeze during peak and given our monthly release cycles it really does not give us any flexibility with resources at the moment - which is what we desperately need. 

 

If there could be consideration for an early 2021 date that would be hugely beneficial as we'd be able to de-risk our peak trading window and get this necessary migration completed. We'd be able to redeploy resources immediately and be able to adapt to this new world we're in. 

 

Avatar

Avatar

thebenrobb

Employee

Avatar

thebenrobb

Employee

thebenrobb
Employee

01-04-2020

@sophiebegley, this isn't necessarily the last adjustment to the dates.  The Milestone 2 date is still over 6 months out, but depending on how the next 2 months play out we make additional extensions.

Avatar

Avatar

FredrikvonS

Avatar

FredrikvonS

FredrikvonS

19-08-2020

I guess that "Milestone 2: 2020-02-16" should be "Milestone 2: 2021-02-16"...

Avatar

Avatar

thebenrobb

Employee

Avatar

thebenrobb

Employee

thebenrobb
Employee

30-09-2020

@FredrikvonS, yes, I've corrected it above.