Import classic editor content to FX Builder

[wolffe]

After the first switch from the classic editor to FX Builder, a meta field should be set, and the content imported.

The ajax_import_data() function can be used, with minor modifications, to allow passing a post ID and then building a fake JSON payload to simulate an import. After the first import, the content of the classic editor should be wiped, and the migrated meta field should be set to 1.

As a UX improvement, the classic editor tab can be hidden, if the migrated meta field is 1.

[xxsimoxx]

If I'm not wrong, when the content is edited in FX Builder, the content is a "flattened" version of the post meta that store the actual page.
What if you leave the content untouched, and use a [content] shortcode, so you can insert anywhere in the layout the post content? This way an user can switch between classic and FX content.
This is how many pagebuilders work.

[wolffe]

Yes, but after the page has been migrated to FX Builder, it can't be switched back, as it was. It will have the new columns and rows classes from FX Builder.

I haven't seen a page builder where switching back will leave a clean version of the content.

And the way you say it, if I leave the content untouched, I will have 2 versions of the content: one from FX Builder and the original one.