Official migration path from the old KrafterPRO Design System to v3.1.2

Hi Mak,

Thank you for continuing to improve KrafterPRO. I would like to raise an important migration issue for users who built websites with the older KrafterPRO Design System before the new plugin and the updated Design System were introduced.

Many existing users may already have complete websites using the old presets, variables, and internal preset IDs. The difficulty appears when importing the new Design System using either Merge or Replace.

With Merge:

• The old and new presets appear together because their names and internal IDs are different.
• For example, an old preset such as k-section medium and the new k-section-m are treated as separate presets.
• This creates duplicate systems, and existing pages continue using the old presets rather than automatically adopting the new ones.
• Users who already used Merge may now have both generations of presets in the same website.

With Replace:

• Existing pages still reference the old internal preset IDs.
• If an old referenced preset is removed, the page design can change because Divi cannot find that ID.
• The new Replace protection in 4.1.24 is helpful because it keeps protected presets and presets still used on pages or in Theme Builder.
• However, retaining those old presets prevents the design from breaking but does not migrate them to the new v3.1.2 presets.
• The result may still be a mixture of old referenced presets and new presets.

The main issue is that matching preset names is not enough because Divi connects page elements through internal preset IDs.

What existing users need is an official migration process that can:

1. Detect websites using the older KrafterPRO Design System.
2. Recognize sites where Merge was previously used and both systems now exist.
3. Map old presets to their correct v3.1.2 equivalents.
4. Preserve or safely update the old internal IDs so existing page references remain connected.
5. Apply the new preset structure and settings without changing the current design unexpectedly.
6. Map old variables and colors to the new token structure.
7. Show ambiguous or unavailable mappings before applying the migration.
8. Provide a backup, preview, or rollback option.

For example, the desired result would be:

k-section medium with its existing old ID
→ receives the correct v3.1.2 structure/settings
→ existing pages remain connected automatically
→ no duplicate old/new presets are required.

We attempted to solve this by creating a custom migration JSON that preserves old IDs while inserting the new preset settings. However, this is delicate because the old and new systems have different preset inventories, names, IDs, variables, and structures.

Is there already an official upgrade or migration tool for websites built with the old KrafterPRO system? If not, would it be possible to add one to the plugin?

I believe this would be very valuable because many existing KrafterPRO users likely created websites before the plugin and the current Design System were available. They need a safe upgrade path, not only a fresh installation workflow.

Thank you, Mak. I would appreciate your advice on the recommended migration procedure for existing production websites.