Drupal 8 upgrade path: Bean Migrate

Yes, I worked with Kris to make sure that bean would be deprecated in Drupal 8. The block type plugin concept is the same as what blocks are in D8 which replaces core bean. Custom blocks are fieldable entities also in D8 which replaces the functionality of bean_admin_ui.

That's been the goal all along!

A likely contrib candidate for d8 could be a migration extension for migrate_d2d that helps slurp in Beans, Fieldable Panels Panes and Boxes from a D7 site and turn them into Core block entities. If anyone would like to work on this together, or talk about the future of D7 bean plugins as D8 block plugins, we're in #drupal-beans...

Did the bean migrate conversation ever go anywhere? I found https://www.drupal.org/node/2141211, but with RC1 "coming soon" it would be really helpful to consolidate the D8 info and share this on the Bean project page.

Since we just use blocks in D8 and have need for a Bean module this makes sense. A bean from D7 to D8 custom block migration can be written but mileage may vary - - I'd check out what's working in migrate for d2d and see if those migrations could be of reference.

Sorry, meant to re-open this not fix it!

I think this is a great idea. Looks like some progress has been made on this thread? Although not sure of the current status.

https://www.drupal.org/node/2295973

Does anyone know if progress is being made on a migration path? Or if anyone has done it using custom migrations?

I would suggest approaching this from the perspective of the Bean module's two main use cases:

• Standalone blocks with fields: Drupal 8's block system supports fields out of the box, so obviously the logical path would be to have a migration path directly to core's block system.
• Referenced entities: Lots of sites used Bean as an entity to be embedded in other content using EntityReference, and some people workied on a patch to allow referenced beans to work with editorial workflows (#1837650: Allow referencing a specific revision ID). The (stable) D8 equivalent of this architecture is Paragraphs so the migration path should be towards Paragraphs rather than blocks.

We're really eager to see sites upgrading from D7 to share code that helps towards either of these use cases, I think some collaboration would go a long way for everyone.

In case it helps somebody, I have an example of a Bean migration here https://github.com/npinos/d7migrate

I've been working on something similar for the ECK module: https://www.drupal.org/project/migrate_eck2blocks

This uses some hooks to change field definitions to block content types, along with some plugins. I think a similar approach could be used for Bean.

My colleague @huzooka has been working on a comprehensive migration for bean: https://www.drupal.org/project/bean_migrate. It's already working well for monolingual beans, he's currently working on finishing multilingual migrations. Including correct block placement migrations.

That's fantastic, amazing work @huzooka!

I'm going to document that as the official upgrade path.