If you are running a Laravel application that has fallen behind on upgrades, you have two practical options for getting it current. The first is hand-coding the upgrade across breaking changes. The second is using an automated tool. There are exactly two automated tools in this category with meaningful market presence: Laravel Shift (commercial SaaS, the longstanding player) and Laravel Ascend (open source, newer, available on GitHub).
This article is for engineering managers and tech leads evaluating both. It is not a sales document. The honest comparison includes where each tool is the better choice and where the other one is. Disclosure up front: Laravel Ascend is a Golden Path Digital open-source project. The analysis below is structured to be useful regardless of which one you pick.
What Both Tools Do
Both tools automate the process of moving a Laravel application from an older major version to a newer one. The work involved in any Laravel major-version upgrade includes:
- Updating composer.json with new constraints
- Applying code transformations for breaking changes (deprecated functions, removed features, new APIs)
- Updating configuration files
- Updating dependencies that themselves have major-version changes
- Resolving conflicts in vendor packages
- Running the test suite to validate
Both tools handle the mechanical portions of this work. Both produce a diff that the engineering team reviews before merging. Both reduce a hand-coded upgrade from days or weeks to hours or minutes for typical applications.
Where the Two Tools Differ
Distribution model
Laravel Shift: Commercial SaaS. You connect your Git repository (typically GitHub or GitLab), select the upgrade target, pay per upgrade, and receive a pull request with the transformations applied. Each upgrade transaction is its own billable event.
Laravel Ascend: Open source under MIT license. Available on GitHub at github.com/goldenpathdigital/laravel-ascend. You install it as a Composer package in your project and run it as a CLI tool. No external service involvement, no per-upgrade fees, no transaction model.
Data flow
Laravel Shift: Your source code is uploaded to Shift’s infrastructure, transformed there, and a pull request is opened against your repository. For most teams this is fine. For teams with strict data residency requirements, source code touching third-party infrastructure may require legal review.
Laravel Ascend: Runs entirely in your local environment or CI pipeline. Source code never leaves the network. No external service involvement at all.
Customization
Laravel Shift: Closed source. The transformations are what they are. If a transformation does not handle your specific case, you raise a support ticket or work around it manually.
Laravel Ascend: Open source. The transformations are visible code. If a transformation does not handle your specific case, you can extend it, contribute back, or fork the project for your specific needs.
Version coverage
Laravel Shift: Covers Laravel versions back to early releases, plus PHP version upgrades, package modernization, and conventions adoption. Broadest scope of automation in the category.
Laravel Ascend: Currently covers Laravel 6 through 11 (the most common upgrade paths in 2026). Focused on the core framework upgrade path rather than the broader ecosystem.
Cost structure
Laravel Shift: Per-upgrade pricing. A single application moving from Laravel 6 to Laravel 11 may require multiple sequential upgrade transactions, each billed separately.
Laravel Ascend: Free. The code is MIT-licensed. The cost to use it is the engineering time required to run it and review the output, same as any internal tool.
Support model
Laravel Shift: Commercial support included with purchase. If a transformation produces incorrect output, you have a vendor relationship to escalate to.
Laravel Ascend: Community support via GitHub issues. Golden Path Digital maintains the project and is the primary committer, but the support model is open-source norms: file an issue, contribute a fix, or work around it locally.
When Laravel Shift Is the Better Choice
Laravel Shift is the right tool when:
- You want a one-click vendor relationship and your codebase can be uploaded externally without compliance concerns
- You need broader automation beyond core framework upgrades (PHP version upgrades, broad package modernization, conventions adoption)
- You have a clear budget for per-upgrade transactions and the volume is manageable
- You value commercial support over self-service troubleshooting
- You are upgrading from very old Laravel versions (pre-6.0) that Ascend does not currently cover
When Laravel Ascend Is the Better Choice
Laravel Ascend is the right tool when:
- Your source code cannot leave your network (regulated industries, defense contractors, certain enterprise compliance regimes)
- You want zero per-upgrade cost (high upgrade volume, multiple applications, ongoing portfolio modernization)
- You want visibility into the transformations and the ability to customize them
- You are upgrading from Laravel 6, 7, 8, 9, or 10 to a current target (the version range Ascend covers)
- You prefer open-source tools as a portfolio strategy
- You want to run the tool in your existing CI pipeline rather than via an external service
The Honest Limitations of Each
Laravel Shift limitations: Closed-source means the transformations are opaque. Per-upgrade cost adds up across portfolios. Cloud-resident transformation is not workable for some compliance regimes. Pricing changes are vendor-controlled.
Laravel Ascend limitations: Narrower version coverage. Smaller scope (core framework upgrade only, not the broader ecosystem). Open-source support model means timelines are not contractually guaranteed. Less mature ecosystem of related tooling.
Both tools have real limitations. The right choice depends on which set of limitations matters less for your specific situation.
The Mixed Approach
Some teams use both. A typical pattern:
- Laravel Ascend for routine Laravel-version upgrades on portfolio applications
- Laravel Shift for one-off complex upgrades that need broader automation (PHP version migration, comprehensive package modernization)
The two tools are not zero-sum. Different applications, different upgrade paths, different tools.
What Neither Tool Replaces
Both tools handle the mechanical transformation work. Neither replaces:
- Test suite execution. The post-upgrade test run is still the test run. If the application has no test suite, an upgrade tool produces less value because no one can validate the output.
- Domain logic review. Breaking changes that touch business logic (deprecated authentication patterns, changed default behaviors) require human review regardless of tool.
- Package-by-package dependency review. When third-party packages have major version changes that affect application behavior, the tool can update versions but cannot understand what the application does with those packages.
- Performance regression testing. Major Laravel upgrades occasionally introduce performance characteristic changes. The tool cannot detect these.
An upgrade tool is a force multiplier on existing engineering practice. It is not a replacement for engineering practice.
What to Do Next
If your team is sitting on a Laravel application that has fallen behind, the next step is to identify the specific source version and target version, then evaluate which tool fits your specific constraints.
For Laravel Ascend, the GitHub repository at github.com/goldenpathdigital/laravel-ascend has documentation, installation instructions, and the source code. It is MIT-licensed and free to use.
For Laravel Shift, visit laravelshift.com for pricing and supported upgrade paths.
For teams modernizing portfolios that include both Laravel and IBM i (RPG) applications, Golden Path Digital builds tooling for both ends of the modernization problem. Visit goldenpathdigital.com for product details, or reach out via the contact form for a discovery call.
Golden Path Digital is an enterprise software and AI modernization company headquartered in Hot Springs Village, Arkansas. AS/Forward modernizes IBM i and RPG codebases. Laravel Ascend automates Laravel application upgrades. QuantaPath AI delivers HIPAA-compliant CRM and workflow automation. Serving enterprises nationwide with US-based delivery and air-gapped deployment options. 1 US patent pending.