Steps to move data from core to contrib

Going to tag a 2.0.0-alpha1 hopefully today

But idea is you can download the module and drop in and that's it. No migration or anything but would test heavily just to be sure.

But idea is you can download the module and drop in and that's it. No migration or anything but would test heavily just to be sure.

That's a really great idea. Hopefully it works exactly as described.
I will report back...

Thank you very much for your work and the time you have invested here.

FYI 2.0x will require 10.3 or 11 and recommend heavy testing

The way I did is:
1. Move your current Drupal version to 10.3.0, in this version, the book module becomes deprecated in the core.
2. Add the book module in the contrib via composer, command given in https://www.drupal.org/project/book →
3. Upgrade your Drupal to Drupal 11.

This ensures legacy data is preserved.
As you already have Drupal version 10.3.2, then you can proceed from second point.

When the Contrib module is activated, the module from the core is also active.

I have two questions about this:
1) Can the core module then simply be deactivated?
2) Will the configuration (content types, blocks ... ) and the created content be retained?

@dbielke1986 You cannot have two different books in core and contrib, only one will be activated even if you try. If you have added Book in contrib then drupal will recognise that contrib module only, else it would recognise the core module.

If you have already installed contrib version via composer then there will not be any configuration loss as I understand the machine name remains valid and hence the configuration is safe with it.

Great, thank you. We will test this in our testing environment and provide feedback.

BR

have a stable release of 2.0.x out