Migration Assistant
Migration Assistant moves pages and media into Capell through preview, validation, execution state, and rollback reports.
What Migration Assistant helps you do
This private package is outside the Released and Beta channels, so no public install path is available.
Workflow screenshots
6 capturesMigration Assistant moves pages and media into Capell through preview, validation, execution state, and rollback reports.
Teams can inspect mappings before anything is written, which reduces migration surprises.
Imports stay supportable because every run leaves a report you can re-check or reverse.
Use it when content migration needs a controlled Capell workflow instead of one-off scripts.
Review the documentation and screenshots on this page before enabling it on a production Capell site.
What changes on your site
Review the admin, public, data, scheduled, and command surfaces Migration Assistant adds when enabled.
- Migration Assistant
- Import
- Export
- Field Mapping
- Preview
- Rollback Reports
Install after you have checked the fit.
Confirm version compatibility, support, data access, migrations, retained data, and removal steps first. Then install the Composer package from the account that owns access.
-
01
Require the package
composer require capell-app/migration-assistant -
02
Register the extension
php artisan capell:extension:enable migration-assistant -
03
Clear schema cache
php artisan capell:admin:clear-schemas-cache
Evaluator scenarios
What to inspect in Migration Assistant
Switch the evaluation lens to see how different roles should assess this package before installing it.
Test Migration Assistant with a site owner
Dry-run a move, inspect the proposed field mappings, then edit an imported record before rollback. No live record should land before confirmation, and the later correction must not be deleted.
Read more Show less
The demonstration should show: Rollback reads a per-record ledger and refuses to delete any page a person edited after import, so an undo never throws away work layered on top. The dry-run tells site owners 'this would remove 40 pages, skip 3 edited ones' before site owners commit to anything.
Scope check: Site owners still need a Laravel developer to drive it, and there's cleanup either way. If the current site is stable and small, staying put can beat migrating.
Release and download evidence
- Total downloads
- 0
- Last downloaded
- No downloads yet
Version history
1 release-
v1.0.0May 3, 2026
Before checkout
Know who owns access and what happens next
Payment, customer account ownership, site activation, and package access are separate steps. The checkout reference lets support trace a problem without moving the licence to another account.
Who processes the payment and taxes?
Lemon Squeezy hosts paid marketplace checkout and issues the tax receipt. Capell does not collect card details; it activates the matching marketplace licence after payment is confirmed.
Which account owns the licence?
The signed-in customer account that completes checkout owns the licence, receipt, support history, and future install access. Use the intended organisation account before paying.
How does the site receive package access?
The install flow connects the licence to the requesting site. Paid and private packages then use authenticated Composer access from the customer account that owns the licence.
What happens if checkout is cancelled or expires?
No licence is created until Lemon Squeezy confirms payment. After a cancellation or expired quote, return to the same marketplace listing and start a fresh checkout so price and package details are recalculated.
What should I do if access does not appear?
Keep the checkout reference from the page or receipt and contact support before trying another account. Support can trace the payment, customer account, licence, and connected site from that reference.
No approved reviews yet. Reviews from eligible customers appear here after moderation.
