Skip to main content
Reactive Resume v6 replaced v5 on rxresu.me. This page explains what happened to your v5 work, and how to bring resumes over from an older copy of Reactive Resume (v5 or v4) that you still have access to.

​
Your v5 work is already in v6

If you used v5 on rxresu.me, you don’t need to do anything. Your account, resumes, cover letters and applications moved to v6 automatically. Sign in at rxresu.me as before to find them in Documents and Applications. A few things look different after the move:
  • Cover letters that were sections inside a resume are now separate letters in Documents, linked to that resume.
  • Dates were converted to months and years. Any date that couldn’t be read exactly still prints as you wrote it.
What’s new in v6 explains these and the other changes.

​
Is v5 still available?

There’s no hosted copy of v5 that you can count on. If you need a resume exactly as it was in v5, your best option is a JSON file you downloaded from v5 earlier, or a v5 copy that you or your organization runs. People who host Reactive Resume themselves can keep running v5 by pinning the v5 image tag (for example, amruthpillai/reactive-resume:v5) on a database that hasn’t been upgraded. v5 isn’t meant to run on a database that v6 has already upgraded, so back up the database first. Server owners should read Migrating from v5 before they update.

​
Move a resume from v5 into v6

If you have access to a v5 copy, export each resume there and import it into v6.
1

Export the resume from v5

In v5, open the resume and download it as JSON. Repeat for each resume you want to keep.
2

Open the New document dialog in v6

Sign in at rxresu.me (or your own address) and select New in the sidebar, or press N.
3

Import the file

Select Import a resume and choose the JSON file. Reactive Resume recognizes the format and shows how many sections and entries it found. Select Open in editor.
4

Review what came in

The editor tells you what it imported, including any dates to check. If the resume contained a cover letter, it’s saved as a separate letter in Documents.
The import always creates a new resume. It never replaces one you already have, so compare the two before deleting either. For more on importing, including other file types, see Importing resumes.

​
Resumes from v4

Version 4 is two versions old. At the time of writing, a copy may still be reachable at v4.rxresu.me, but its availability isn’t guaranteed. If you can sign in there, open each resume, export it as JSON, and import it into v6 as described above. v6 recognizes v4 files automatically. Server owners moving a self-hosted v4 installation should follow Migrating from v4 first, then Migrating from v5.

​
If something is missing

If a resume you expect is missing from v6, ask for help in GitHub Discussions. Describe what’s missing and roughly when you last edited it. Don’t post resume contents, passwords, reset links or other private details.