# Migrating FROM mysql back to sqlite

**URL:** <https://vaultwarden.discourse.group/t/migrating-from-mysql-back-to-sqlite/685>\
**Category:** Help\
**Created:** [March 6, 2021, 12:42am UTC](https://vaultwarden.discourse.group/t/migrating-from-mysql-back-to-sqlite/685 "2021-03-06T00:42:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![derzahla](https://avatars.discourse-cdn.com/v4/letter/d/f9ae1b/32.png) [@derzahla](https://vaultwarden.discourse.group/u/derzahla)\
**Post date:** [March 6, 2021, 12:42am UTC](https://vaultwarden.discourse.group/t/migrating-from-mysql-back-to-sqlite/685/1 "2021-03-06T00:42:37Z")

</div>

Hi. So a few months ago I decided to migrate bitwarden from sqlite to my centralize mysql instance. Everything worked perfectly!

Now though, for ease of backup(would like to zfs send my entire bitwarden jail to another location) I would prefer to go back to sqlite. I’ve tried using this script ([mysql2sqlite/mysql2sqlite at master · dumblob/mysql2sqlite · GitHub](https://github.com/dumblob/mysql2sqlite/blob/master/mysql2sqlite)) to convert the mysql dump to sqlite. It seemed to mostly work, however, when I tested logging out and back in my password was no longer recognized. Is there any supported way of going from mysql back to sqlite? Any suggestions would be much appreciated!

As a side note, are there any HA solutions for bitwarden\_rs?

Thanks!

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [October 22, 2021, 4:03pm UTC](https://vaultwarden.discourse.group/t/migrating-from-mysql-back-to-sqlite/685/2 "2021-10-22T16:03:36Z")

</div>

See: [Migrating from MariaDB (MySQL) to SQLite · dani-garcia/vaultwarden Wiki · GitHub](https://github.com/dani-garcia/vaultwarden/wiki/Migrating-from-MariaDB-%28MySQL%29-to-SQLite)

---

<div class="post-metadata">

**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\
**Post date:** [October 22, 2021, 4:14pm UTC](https://vaultwarden.discourse.group/t/migrating-from-mysql-back-to-sqlite/685/3 "2021-10-22T16:14:22Z")

</div>

There is no HA available. If you search this forum you should find some articles which will explain what could work and what not.

---

<div class="post-metadata">

**Author:** ![cksapp](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@cksapp](https://vaultwarden.discourse.group/u/cksapp)\
**Post date:** [October 22, 2021, 4:17pm UTC](https://vaultwarden.discourse.group/t/migrating-from-mysql-back-to-sqlite/685/4 "2021-10-22T16:17:12Z")

</div>

> [@derzahla](#):
>
> As a side note, are there any HA solutions for bitwarden\_rs?

To respond here as this is something I’ve looked at wanting to play with, it would mostly depend on your implementation of Vaultwarden I believe.  
Not sure how Vaultwarden would act with SQLite on a shared storage (most likely would not imaging it would work well being “opened” by multiple Vaultwarden instances, but perhaps in a failover situation), but I would imagine the easiest would be to use a truly shared database such as MariaDB or PostgreSQL, connected to multiple Vaultwarden containers, all behind a load balancer.