What should an app let you take when you leave?

You cancel a project management app and download your data. The spreadsheet has every task title, but the attachments are gone and the comments that explain the decisions are missing.

An export can serve very different needs:

  • A file you can open and read later.

  • A backup that keeps attachments and history together.

  • A format another app can actually import.

Each is useful, and a small team may only have time to do one well.

Think of the last app you left. What did you need to take with you to keep working?

57 views

Add a comment

Replies

Best

all my data in a format I can open somewhere else, plus anything I made with it. funny thing is when leaving is easy I usually stay longer

From the builder's side: It is a small project, so I only picked a plain file you downloaded and kept. No import into other apps. It's honest, but less convenient for the person leaving. Which of those three do your users actually ask for when they go?

 I don't have a clear answer from users yet. I'd start with an export that keeps task IDs alongside comments and attachments. Then someone can still tell which files and decisions belong to each task, even if they rebuild the project by hand.

+ A backup that keeps attachments and history together.

Our team is capable of building the import and conversion to another application ourselves. We've already done it twice. However, the export archive needs to be complete, including files, comments, and everything else that was there.

From the SEO side, what people need when they leave is proof of work they can check without us. When we built link reports at PromoPilot, the export that mattered was boring: every placement URL plus whether that page is indexed in Google. Without it, a client who leaves can't tell which of the work still exists.

So my vote is the readable file, but with stable IDs and original URLs, not just titles. A file that points to things outside the app ages much better than a backup only the app itself can restore.

Has anyone had an export break later because the links inside it pointed back into the app they left?

 I'd test the export in a signed-out browser. Keep links to external placements, but bundle files the app hosts and use relative links in the archive so they still open after the account closes.

 the signed-out browser test is a good one, simple and brutal. It would also catch the case where a report link quietly redirects to a login page. Bundling hosted files with relative paths makes sense too, the archive becomes a small offline site instead of a list of dead links.

Do you plan to add a date to each item in the archive? For external links that matters, because the page we checked last month may not look the same today.

 I’d keep two dates: when each external link was last checked and when the archive was exported. That way a fresh download doesn’t make a month-old check look current.

 two dates makes sense. For link reports that's exactly the trap: an "indexed" status with no check date looks like it's true today, even if it was checked weeks ago. Thanks for the back-and-forth, this thread turned into a decent export checklist.