A campaign owner has three email drafts, a revised offer, and a launch date buried in a conversation. A workspace update is approaching. The useful backup is a verified export packet: saved prompts, readable campaign records, email files, and a short list of what the packet cannot restore. Downloading a file is only the first step.
Adobe's CX Enterprise Coworker notice updated October 8, checked October 14, schedules app unavailability from October 14 at 10 p.m. PDT through October 16 at 6 a.m. PDT. Existing conversations, campaigns, and data will not carry over. If you use this Adobe product, save important prompts locally and export campaigns as PDF or Word and emails as HTML before October 14 at 10 p.m. PDT. This notice concerns CX Enterprise Coworker, not every Adobe service.
Start with a packet you can inspect
This fictional inventory shows a small creator campaign. The filenames and review outcomes illustrate the method; they are not customer evidence. Use one private folder for the packet and keep this inventory inside it.
| Project | Last revision | Export filename | Open check | Owner | Missing items |
|---|---|---|---|---|---|
| Desk lamp launch | Offer v4, Oct. 14 | lamp-plan-v4.pdf | Pages and dates checked | Campaign lead | Editable journey state |
| Desk lamp launch | Welcome email v3 | lamp-welcome-v3.html | Text and links checked | Email editor | One remote image |
| Desk lamp launch | Reminder email v2 | lamp-reminder-v2.html | Opened; offer corrected | Email editor | Final approval |
| Desk lamp launch | Brief v5 | lamp-prompts-v5.txt | Instructions and sources present | Campaign lead | Earlier discarded drafts |
The goal is an honest record of what survived. A row marked 'downloaded' leaves too much unknown. 'Opened; offer corrected; final approval missing' tells the next editor what they can use and what still needs a decision.
Capture the decisions behind the draft
Copy the useful prompts with their current answers and source references. Keep the goal, audience definition, approved offer, exclusions, tone, and timing together. Label superseded instructions. A folder containing both a 15 percent discount and a later 10 percent discount needs a clear current decision, not a guess during rebuilding.
Record who approved each material change and where the approval can be checked. Preserve a reference to a private approval record rather than copying an entire confidential conversation. Retain only the audience information the rebuild actually needs; a segment description is different from a contact list.
If several people edited the campaign, name one owner to reconcile revisions. Each contributor can export their work, but someone must decide which version represents the campaign at the cutoff. Use the AI agent evaluation task pack to define observable checks for a proposed reconstruction.
Open every file before calling the packet complete
Adobe's Campaigns overview also documents individual email HTML exports and full campaign Word or PDF exports for review. Choose the formats you can inspect with the tools already available to you.
Open the PDF or Word document and check page count, readable text, journey order, offer details, and dates. Open the HTML email and inspect its text, destination links, image references, and footer. A file can open successfully while depending on remote images or styles that are absent from the folder. Record those dependencies and use your own approved assets when rebuilding.
Do not treat an attractive preview as a complete verification. Follow each important link to confirm its destination. Compare the exported version with the latest approved copy. If an image fails, identify the missing asset in the inventory rather than hiding the gap behind a screenshot. Keep the original export untouched and put corrections in a separate review copy.
Keep records and restore instructions separate
A PDF, Word document, or HTML email is a review record. It does not establish that you can automatically restore editable campaign boards, permissions, integrations, or conversation history. Write a separate rebuild note stating what must be recreated and what remains unverified.
Use a short order: restore the approved brief, reconstruct the draft artifacts, inspect the links and assets, then request review. Carry permissions and connected services as explicit questions for the relevant owner. An old permission record is evidence of an earlier arrangement, not authorization for a new connection.
For campaigns in several languages, preserve the approved language versions separately. The campaign localization review brief helps reviewers compare claims, dates, and calls to action without assuming every translated draft shares the same approval.
Review the rebuild before any release
Store campaign files in a private location your team controls, outside a public blog or source repository. Check that another authorized reviewer can open the packet. Keep a second copy where your existing storage policy permits, and label both with the revision and export time.
For Growit o1, follow the current account-specific availability and workflow instructions in o1 guides. This backup plan does not promise an automatic migration service or live background reconstruction. The physical pocket device remains in development; o1 specifications describe its current status.
Before the applicable cutoff, finish the inventory, resolve missing files, and name the rebuild owner. After access returns, compare the proposed reconstruction against the packet. Approve that draft separately from any publishing or sending decision. A migration deadline should produce a checked handoff, not a rushed campaign release.