ページ · Laravilt
Post-Migration Checklist
Review, register and test your code after migrating from Filament.
1. Review Generated Files
2. Check the Panel Provider
If your panel provider uses discoverAutomatically() (the default from laravilt:install and laravilt:panel), migrated classes in app/Laravilt/Admin are picked up automatically. Otherwise, register them:
3. Build Frontend Assets
$ pnpm build4. Test CRUD Operations
Test create, read, update and delete for every migrated resource. Check that resources declare protected static string $model and protected static int $navigationSort with those exact types.
5. Remove Filament (Optional)
Manual Adjustments
Custom Livewire Components
Laravilt uses Inertia instead of Livewire. Rewrite custom Livewire views as Vue components (.vue) or React components (.tsx), depending on your stack.
React support requires Laravilt v1.1 or later.
Complex Relationships
Review relation managers and consider nested resources for deep hierarchies.
Custom Actions
Review actions with complex logic.
Plugins
Filament plugins are not converted. Check the plugins section for Laravilt equivalents.
Troubleshooting
Source directory does not exist
Pass --source if your Filament classes live elsewhere.
Namespace Conflicts
Use --force to overwrite existing files, or merge by hand. Run with --dry-run first to preview.