Skip to main content
Srinija_N
Adobe Champion
Adobe Champion
Oct 31, 2026 6:48 AM UTC

Best practices for decommissioning a Workfront instance

Our org is currently exploring options for decommissioning a client’s Adobe Workfront instance. Specifically, we'd like to understand the different approaches available such as permanent deletion versus archiving, along with the pros and cons of each method.

If your organization has gone through this process, what approach did you take, and what recommendations do you have?

 

Thanks in advance for sharing your insights!

4 replies

HeatherRo13
Adobe Champion
Adobe Champion
Nov 2, 2026 12:16 PM UTC

Hi! Will any of the existing data be migrated to a new system of record or will it all just be a historical record for reference after a cut off date?

Translate
Srinija_N
Adobe Champion
Srinija_NAdobe ChampionAuthor
Adobe Champion
Nov 4, 2026 6:52 AM UTC

Hi ​@HeatherRo13 , Thanks for the question!

The current thinking is to retain the existing Workfront data mainly for historical reference after the cut-off date, with only selected business-data potentially moving to another system. We’re exploring the best way to handle this, so I’d definitely be interested to hear what approach you’d recommend.

Translate
Srinija N
HeatherRo13
Adobe Champion
Adobe Champion
Nov 4, 2026 10:38 PM UTC

OK, one last question since i don’t know your agreement with Adobe, will you still have access to view records in Workfront or will there be a cutoff date where all access ends?
Note: There is no real “Archive” functionality for most Workfront objects.  You would only need to delete if there was a storage issue, otherwise you can use statuses and/or custom fields to close things out or mark for migration.

Translate
Russ_Nelson
Level 2
Nov 16, 2026 7:47 PM UTC

Since there’s no true archive for most Workfront objects (as Heather said), the real decision is usually export, validate, then retire, not archive vs. delete. Here’s the order I’d work in:

1. Define what “historical reference” means. Who will need to look things up after cut-off? What will they look for (project, request, document, approval), and how long do you have to keep it? Your retention and legal-hold requirements decide the format more than anything else.

2. Pick an export method. Adobe’s Export historical data from Adobe Workfront: Pros and cons lays out the options:

  • Reports / Kick-Starts: free if a system admin runs them, and easy to read and import elsewhere. Documents have to be downloaded separately. See Export data via Kick-Starts.
  • API: you control exactly what comes out, but someone has to build it and run it.
  • Partner app (Workfront Snapshot from AtAppStore): exports core objects, including custom fields and notes, to an Access database with an offline viewer. It has a 2 GB data limit, and document extraction is a separate service.

3. Plan around export limits. Per Export data, the row limits are 100,000 for .xlsx, 65,000 for .xls, and 50,000 for PDF and tab-delimited. Reports that run longer than 60 minutes are halted. Split big objects (tasks, hours, updates) by year or portfolio with filters or prompts.

4. Don’t forget what isn’t rows: documents and their versions, update threads, proof and approval history, custom form definitions and templates. Decide which of these matter for reference, and test the export of each before cut-off.

5. Validate, then close out. Reconcile record counts between the export and the instance, and get sign-off from the data owners. Mark records as retained or migrated with a status or custom field (Heather’s suggestion). Before you rely on the instance staying available, confirm with your Adobe account team what happens to its data at contract end.

Delete only after the export is validated and retention is signed off. Deleting early buys you very little, and it’s the one step you can’t undo.

Translate
Russ Nelson, Founder, Prolifico Digital