I started to testing vikunja and as already said in other posts: It’s damn f* great! :rocket: To have a fast start, I used sqlite as the backend database. Now I want to reinstall vikunja on my productive server with valkey and postgresql. I can’t export my data of vikunja because it wants to send …

To summarize the solution: ▶ 1. Use pgloader tool to migrate Vikunja's SQLite DB to PostgreSQL ▶ 2. Convert all boolean DB columns in PG from bigint to boolean type

OMG, that sounds crazy! :exploding_head: So you have seen everything when you survived with Oracle not true? Yes I found also pgloader, don’t get me wrong I google first before I created the post, but the tool is only available for Debian systems - I thought! So I created this post here, maybe you…

Did you change this env variable to postgres? If not - I would advise to do the conversion from scratch. Try changing the SQL log level to see what query exactly fails. See code snippet with needed env variables here: Dev: how to log DML SQL queries P.S. it’s always worth checking if such tools …

If you mean the database section in the config.yml, yes: database: # Database type to use. Supported values are mysql, postgres and sqlite. Vikunja is able to run with MySQL 8.0+, Mariadb 10.2+, PostgreSQL 12+, and sqlite. type: "postgres" # Database user which is used to connect to the datab…

It’s worth checking PG log to get the timestamp of when error happens, then checking desktop/SQL logs around that time to see possible culprit DB tables, then setting up alternative Vikunja env on PG and comparing DB types between discovered DB tables.

I probably found the culprit: [image] The Sequences objects are not the same as you see in the reference picture. Keep in mind that the devdb is the one which I tested the import or better say the migration from SQLite to PostgreSQL, where the devdb2, I know super name, is the new one which is cr…

You need to make sure sequences in SQLite and converted PG are the same - same amount, same names, same values. Also sequences don’t sound like they have something to do with original error pq: invalid input syntax for type bigint: “false”, but maybe you’re right. [image] LxWulf: my second tho…

I tried different approaches, even though the database errors do not go away… Probably need to redefine the task by hand again… [image] executed: I think this approach won’t work because of ID differences, dependencies, etc. Yes, it didn’t work. [image] executed: P.S. how many tasks yo…

Update: I found out that if you select Export in the Settings of Vikunja it creates a zip file in the root path of the binary or whatever is configured via config.yml file. Though it does not have a real filename or extension. In my case, it’s just called 8. [root@pro-00000006-vkja files]# ll tota…

Yeah, that’s unfortunate. I had same error with data import back in the day: [image] Error during data import from Vikunja Export (Project view does not exist) Bug Cannot import data originally exported from Vikunja (same version). Getting Internal Server err…

Okay, I see…so there is no solution to this at the moment?…:disappointed_relieved:…

DB conversion: SQLite to PostgreSQL

Support

executed 25 February 2025 11:42 11

Yeah, that’s unfortunate.
I had same error with data import back in the day:

Topic		Replies	Views
Vikunja data import on self-hosted install gets a 502 Bad Gateway Support	37	1644	10 May 2023
Todoist import not starting on fresh installation Support	1	131	27 February 2024
Wrong credentials after updating images Bug	23	590	12 January 2024
Trello Import Issues Support	27	1327	28 March 2024
How to migrate from 0.24.6 to unstable Support	11	282	15 July 2025

DB conversion: SQLite to PostgreSQL

Related topics