opensaas-migration

Migrate to OpenSaaS Stack by mapping your Prisma models to OpenSaaS lists, installing required packages with lockfile detection, and updating your configuration to opensaas.config.ts. The migration skill provides step-by-step guidance from installation through validation and deployment.

Yes, KeystoneJS migrations to OpenSaaS preserve your file structure and alignment with cross-adapter compatibility. The skill covers access control design, schema mapping, and in-place migration planning without requiring a full project rebuild.

Access control migration to OpenSaaS involves aligning your current permission design with OpenSaaS patterns, configuring role and policy rules in opensaas.config.ts, and mapping existing access rules to OpenSaaS's authentication and authorization modules.

Next.js migrations to OpenSaaS require configuration updates for opensaas.config.ts and alignment with OpenSaaS's UI and authentication modules, but the migration skill provides guidance on preserving your existing structure while adopting OpenSaaS conventions.

Prisma migrations focus on model mapping and schema translation, while KeystoneJS migrations emphasize in-place adaptation and plugin compatibility. Both paths cover access control and config updates, but KeystoneJS preserves more file structure during transition.

Yes, the migration playbook includes test and deployment considerations. The skill provides validation steps to ensure your models, access control, and configuration work correctly before production deployment.