What normally transfers
Eloquent records, media, policies, tests, deployment, and useful Filament resources can often stay in the application. The resources and model logic owner identifies domain screens that remain purposeful and records page-specific logic that needs a new home.
What needs mapping or rebuilding
Repeated page schemas, layouts, URL handling, previews, metadata, history, media reuse, and publishing behaviour need a target in Capell or an optional package. The route owner maps slugs, bindings, middleware, canonicals, redirects, and cache invalidation.
What may not transfer cleanly
Undocumented observers, custom actions, global scopes, policy shortcuts, bespoke panel pages, and implicit editor habits may resist direct mapping. The custom action owner records validation, side effects, jobs, notifications, and authorisation; the editor expectation owner decides what the replacement task must preserve.
Verify URLs and search metadata
Inventory titles, descriptions, canonicals, language paths, media references, routes, redirects, sitemaps, and cache keys. The public-output owner checks anonymous HTML contains no editor metadata and verifies a representative URL sample before migration, during the pilot, and after cutover.
Run a representative pilot
Choose one routine page and one difficult page family with custom model logic, actions, routes, reused media, and editor expectations. Keep existing domain resources alongside it. Verify the editor task, public response, policies, redirects, metadata, events, jobs, tests, and rollback.
Plan cutover and rollback
The cutover owner assigns one source of truth for every record and URL, freezes writes where needed, switches a bounded route group, monitors errors and redirects, and keeps the old resource or route recoverable until acceptance passes.
Expand only when the pilot proves the shared page model removes recurring maintenance. If the current screens remain few, stable, and application-specific, keep the custom Filament admin.
