Data Migration #2848

Closed
opened 2026-02-05 05:27:19 +03:00 by OVERLORD · 4 comments
Owner

Originally created by @rmfooty on GitHub (Jun 13, 2022).

Attempted Debugging

  • I have read the debugging page

Searched GitHub Issues

  • I have searched GitHub for the issue.

Describe the Scenario

Hi.

I am trying to books over manually to a new instance. When I migrate the Books table, it will not show any of the import data. It will only show new books that have been created using the UI.

Has anyone else had the same issue.

Exact BookStack Version

v22.04.2

Log Content

No response

PHP Version

8

Hosting Environment

AWS Ubuntu 22.04

Originally created by @rmfooty on GitHub (Jun 13, 2022). ### Attempted Debugging - [X] I have read the debugging page ### Searched GitHub Issues - [X] I have searched GitHub for the issue. ### Describe the Scenario Hi. I am trying to books over manually to a new instance. When I migrate the Books table, it will not show any of the import data. It will only show new books that have been created using the UI. Has anyone else had the same issue. ### Exact BookStack Version v22.04.2 ### Log Content _No response_ ### PHP Version 8 ### Hosting Environment AWS Ubuntu 22.04
OVERLORD added the 🐕 Support label 2026-02-05 05:27:19 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Jun 13, 2022):

Hi @rmfooty,
We don't really support partial migration of specific tables from one instance to another.
There's a lot of related data in connected tables which will impact things.
For example, you're likely not seeing content since the related permisison data does not exist in the system.

If possible, you'd generally want to migrate the entire database as a whole otherwise you will likely face issues.

@ssddanbrown commented on GitHub (Jun 13, 2022): Hi @rmfooty, We don't really support partial migration of specific tables from one instance to another. There's a lot of related data in connected tables which will impact things. For example, you're likely not seeing content since the related permisison data does not exist in the system. If possible, you'd generally want to migrate the entire database as a whole otherwise you will likely face issues.
Author
Owner

@rmfooty commented on GitHub (Jun 13, 2022):

Hi @ssddanbrown.

We are trying to migrate the application from an old instance to the current version. Unfortunately we cant do a direct migration as the table fields have changed on a few tables. We have added the new fields and then found that the data was not showing. Even if we modify a simple book record with no other dependencies, it wont show in the UI.

@rmfooty commented on GitHub (Jun 13, 2022): Hi @ssddanbrown. We are trying to migrate the application from an old instance to the current version. Unfortunately we cant do a direct migration as the table fields have changed on a few tables. We have added the new fields and then found that the data was not showing. Even if we modify a simple book record with no other dependencies, it wont show in the UI.
Author
Owner

@ssddanbrown commented on GitHub (Jun 13, 2022):

We are trying to migrate the application from an old instance to the current version. Unfortunately we cant do a direct migration as the table fields have changed on a few tables.

You should not need to do any manual database changes. BookStack will auto-migrate old app database versions to newer versions as needed. You should just export & backup your old clean database, then restore into an empty database on the new system then run the BookStack update commands.

Even if we modify a simple book record with no other dependencies, it wont show in the UI.

Again, you'll be fighting the permission system. We have commands to regenerate permission system intermediate tables but you should ideally update/migrate your data as above as there are many issues you may run into with partial data migrations.

@ssddanbrown commented on GitHub (Jun 13, 2022): > We are trying to migrate the application from an old instance to the current version. Unfortunately we cant do a direct migration as the table fields have changed on a few tables. You should not need to do any manual database changes. BookStack will auto-migrate old app database versions to newer versions as needed. You should just export & backup your old clean database, then restore into an empty database on the new system then run the BookStack update commands. > Even if we modify a simple book record with no other dependencies, it wont show in the UI. Again, you'll be fighting the permission system. We have commands to regenerate permission system intermediate tables but you should ideally update/migrate your data as above as there are many issues you may run into with partial data migrations.
Author
Owner

@rmfooty commented on GitHub (Jun 13, 2022):

Worked like a dream. Thanks for your help :)

@rmfooty commented on GitHub (Jun 13, 2022): Worked like a dream. Thanks for your help :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#2848