Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how to migrate data from old subscription app to new self-hosted instance #25

Closed
hpfast opened this issue Jun 16, 2022 · 4 comments · Fixed by #101
Closed

how to migrate data from old subscription app to new self-hosted instance #25

hpfast opened this issue Jun 16, 2022 · 4 comments · Fixed by #101
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@hpfast
Copy link
Contributor

hpfast commented Jun 16, 2022

Short version: After some searching, I figured out how to migrate my data to my new self-hosted server. This issue documents how. I'll happily open a PR to update the documentation if desired. The workaround is to log in to https://app.actualbudget.com which includes the 'export data' button.

Longer version: I could not find any docs or issues detailing how to migrate from the subscription service to the new self-hosted version. I found references to new releases of the Actual Electron App that allow exporting, but that version has not yet been released and installing/building is non-trivial (I have not succeeded yet).

The (temporary) workaround, which I could not find mentioned anywhere, is to log in to the old web version (https://app.actualbudget.com) which runs the latest version of the app, and includes the 'export data' button (under 'settings' from the menu by the Filename). This allows exporting the data, which can then be imported into the web app pointing at your self-hosted server instance. (getting the latest version of the Electron app in order to point it to the self-hosted server is another matter).

Perhaps I could find no issues mentioning this because I'm the only one who didn't think to try this approach ;) ... but I thought I'd mention it for completeness. As I said, I will happily PR to add this to the documentation if desired -- maybe not desirable if a new release is coming soon?
This issue can be closed otherwise. I will close it in a few days if no reply.

@rich-howell rich-howell transferred this issue from actualbudget/actual-server Oct 20, 2022
@rich-howell rich-howell added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Oct 29, 2022
@tjfinlinson
Copy link
Contributor

Does this still need to be added into the documentation? And if so, what section should it be put under?

@j-f1
Copy link
Contributor

j-f1 commented Feb 8, 2023

I believe it does! Probably under the “Migration” section, and then link to it from a few relevant places.

@hpfast
Copy link
Contributor Author

hpfast commented Feb 8, 2023

Hi, I missed that this had been picked up (and forgot to close it as I had said ...) I'm happy to prepare a PR if you'd like @tjfinlinson

@tjfinlinson
Copy link
Contributor

@hpfast

That would be great. It seems like it would be good to have this on the docs site to provide direction on migrating from the closed source to open source versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants