sugar-mb-export-flow

To convert a Module Builder export zip to an MLP for SugarCRM, run the sugar-mb-export-flow skill to fix doubled prefixes, switch class names, change labels to vnames, remove help texts, and ensure proper metadata file counts.

Module Builder exports often contain quirks like doubled prefixes and incorrect class names. This Skill addresses these specific MB export issues by cleaning up the module structure and switching class names during the MLP conversion process.

The best way to prepare a SugarCRM MB export for installation is to convert it into a deployable MLP. This process handles changing labels to vnames, removing help texts, and verifying proper metadata file counts for a clean installation.

You cannot use a raw Module Builder export directly without encountering deployment quirks. You must first convert the MB export zip into an MLP by switching class names and ensuring proper metadata file counts before installing it.

To fix missing metadata files in a SugarCRM Module Builder export, use an MLP conversion process that ensures proper metadata file counts. This cleanup step prepares the module for a successful deployment in your SugarCRM instance.