Getting Started

WordPress to Laravel: 15 Concepts and Their Equivalents

By Lara Dashboard 1 view
WordPress to Laravel: 15 Concepts and Their Equivalents
If you have built WordPress sites for years, moving from WordPress to Laravel can feel like starting over. It is not. Most of the ideas you use every day have a Laravel equivalent. They just have different names, and they live in different places.
Here is the quick answer. Plugins become Composer packages or modules. Themes become Blade views. functions.php becomes a service provider. Hooks become events, or a hooks package if you want the same style. Custom post types become Eloquent models. WP-Cron becomes the task scheduler, and WP-CLI becomes Artisan. The table below maps 15 concepts, and the sections after it explain the ones that trip people up.
A quick disclosure. We build Lara Dashboard, an MIT Laravel CMS, so we mention where it fills a gap. Every concept here also works in plain Laravel, and we say so. Lara Dashboard facts come from our public repository as of November 2026.

The 15 WordPress concepts and their Laravel equivalents

Read the table as a translation sheet. The middle column is plain Laravel. The last column shows what Lara Dashboard adds on top, so you can see where the WordPress habits carry over.
WordPress conceptPlain Laravel equivalentIn Lara Dashboard
1. PluginsComposer packagesModules you can enable, disable or upload as a ZIP
2. ThemesBlade views, layouts and componentsTheme modules, switched in the admin
3. functions.phpService providersEach module has its own service provider
4. Actions and filtersEvents and listenersld_add_action and ld_add_filter, built on Eventy
5. Custom post typesEloquent models and migrationsregister_post_type() for content types
6. TaxonomiesModel relationshipsregister_taxonomy(), categories and tags
7. Post meta and ACFColumns, JSON casts or a meta tablePost meta with getMeta() and setMeta()
8. WP_QueryEloquent queries and scopesget_posts() and get_post() helpers
9. $wpdb and dbDeltaQuery builder and migrationsSame, plus migrations per module
10. Options APIconfig files and .envget_setting() and update_setting(), with autoload
11. TransientsThe Cache facadeSame
12. Roles and capabilitiesGates and policiesRole editor on spatie/laravel-permission
13. NoncesCSRF tokens and signed URLsSame
14. WP-CronTask schedulerScheduled jobs for updates, inbound email and logs
15. WP-CLIArtisanExtra commands such as module:make and core:upgrade
If you are still deciding whether to move at all, read our decision guide on WordPress, headless or Laravel first. This post assumes you have chosen Laravel and want to get productive fast.

Plugins become packages, and a module system brings back the on/off switch

In WordPress, a plugin is a folder you drop into wp-content/plugins and activate. In Laravel, the closest thing is a Composer package. You install it with composer require, and Laravel often registers it for you through package discovery.
What you lose is the admin switch. A package is either installed or not. That is fine for libraries, but agencies often miss the ability to turn a feature on for one client and off for another.
Lara Dashboard brings that back with modules built on nwidart/laravel-modules. Each module carries its own models, migrations, routes, views and permissions. You can enable or disable it in the admin, or upload it as a ZIP. Our post on modular Laravel apps vs WordPress plugin spaghetti covers why that structure ages better than 30 plugins sharing one database.

Themes become Blade views, and functions.php becomes a service provider

A WordPress theme mixes templates, assets and a lot of logic in functions.php. Laravel splits these apart. Templates are Blade views, layouts and components. Startup logic, such as registering bindings or listeners, lives in a service provider.
Shortcodes deserve a note here. The nearest Blade idea is a component, such as <x-pricing-table />. Components take typed attributes and live in their own files.
In Lara Dashboard, a theme is a module with "theme": true in its module.json. You pick the active theme in the admin, much like Appearance in WordPress.

Hooks become events, or you keep the WordPress style

WordPress runs on actions and filters. add_action() reacts to something. add_filter() changes a value on its way through. The WordPress hooks guide describes them well.
Laravel's native answer is events and listeners. An event is a class, such as OrderShipped, and listeners react to it. This covers actions. There is no built-in filter system, because Laravel usually changes values through pipelines, middleware or plain method calls.
If your team thinks in hooks, Lara Dashboard ships a hooks layer on the tormjens/eventy package. You call ld_add_action(), ld_add_filter(), ld_do_action() and ld_apply_filters(), and hook names are PHP enums, so your IDE can autocomplete them. One gotcha: the helper's default priority is 20, not 10 as in WordPress. Our guide to Laravel hooks and filters has full examples.

Custom post types become models, but you can keep register_post_type()

In WordPress, everything is a post. Products, events and team members all share the wp_posts table, with extra fields in wp_postmeta. In Laravel, each kind of data usually gets its own Eloquent model and its own table, defined by a migration.
That is the biggest mental shift. A product has a real price column, a real foreign key to its brand, and a real index. Reports become normal SQL instead of meta queries. We go deeper in custom post types vs Laravel models.
Not everything needs its own table, though. Editorial content, such as case studies or FAQs, fits a post-style model well. Lara Dashboard keeps that pattern. You can call register_post_type() and register_taxonomy() from a module, and get admin screens, categories and tags without a new migration. Use real models for business data, and post types for content.

Post meta becomes columns, casts or a meta table

ACF and post meta store fields as key and value rows. In Laravel, you have three better-typed options. Add a column when the field is queried or sorted. Use a JSON column with an array cast for loose settings. Use a separate meta table only when fields truly vary per record.
Lara Dashboard posts have a post meta table, with $post->getMeta('key') and $post->setMeta('key', $value). That makes WordPress imports simple. For new business data, we still recommend columns.

WP_Query and $wpdb become Eloquent and the query builder

WP_Query takes a big array of arguments. Eloquent uses chained methods instead, such as Post::where('status', 'published')->latest()->paginate(10). You can wrap common filters in query scopes, so Post::published() reads like plain English.
Raw $wpdb calls map to the query builder through the DB facade. Table changes that you once made with dbDelta() become migrations. Migrations are versioned files in Git, so every environment gets the same schema, and you can roll back.
For theme code, Lara Dashboard also has familiar helpers such as get_posts(), get_post(), get_permalink() and get_post_terms(). They return Eloquent models and paginators, not WordPress objects.

Options, transients and nonces map to config, cache and CSRF

Options. In WordPress, get_option() stores almost everything in one table. Laravel splits it. Secrets and per-server values go in .env. App defaults go in config/*.php. Values that admins change at runtime need a settings table. Lara Dashboard has one, with get_setting(), update_setting() and an autoload flag, much like the Options API.
Transients. set_transient() becomes Cache::put(), and the common pattern becomes Cache::remember(). The cache docs list drivers such as Redis, database and file.
Nonces. WordPress nonces protect forms and links. Laravel adds a CSRF token to every session and checks it on every POST, PUT, PATCH and DELETE request. You add @csrf inside the form. For links that must not be tampered with, use signed URLs.

Roles and capabilities become gates, policies and permissions

WordPress checks current_user_can('edit_posts'). Laravel has gates and policies. A policy is a class that answers a question such as "can this user update this post?" You call it with $user->can('update', $post) or the can middleware on a route.
Laravel has no role editor out of the box. Most teams add spatie/laravel-permission, which stores roles and permissions in the database. Lara Dashboard ships that package with a role and permission editor, plus an admin "login as" feature behind its own permission. See our role-based access control guide for patterns.

WP-Cron becomes the scheduler, and WP-CLI becomes Artisan

WP-Cron runs when someone visits the site, as the WordPress cron docs explain. On quiet sites, jobs run late. Laravel's task scheduler uses one real server cron entry that runs php artisan schedule:run every minute. You define jobs in code, with methods such as ->daily(). Long work goes to queues instead of a page load.
WP-CLI maps to Artisan. You run migrations, clear caches and create files from the command line. Lara Dashboard adds commands such as module:make, module:make-crud, make:block and core:upgrade. Our tutorial on building a Laravel module step by step uses them.

What plain Laravel does not give a WordPress developer

This is where many WordPress developers get stuck. Laravel is a framework, not a CMS. Out of the box, there is no admin area, no media library, no menu editor, no block editor and no content REST API. You build or install each one.
You can assemble them. Spatie's media library handles uploads. Filament or Nova gives you admin screens. Sanctum handles API tokens. That works, but it is real setup work before an editor can publish anything.
Lara Dashboard ships those parts in one MIT app on Laravel 13, PHP 8.3+ and Livewire 4. It has posts, pages, a media library on spatie/laravel-medialibrary, nested menus, the LaraBuilder block editor, a Sanctum REST API with Scramble docs, and an optional MCP server for AI agents. Read how LaraBuilder works if Gutenberg is what your editors will miss most.

Trade-offs: when not to move, and when not to use Lara Dashboard

Moving to Laravel is not always the right call. Be honest about these cases.
  • The site is a brochure or blog, and editors are happy. WordPress is cheaper to keep.
  • Your client depends on a large plugin, such as a full e-commerce or LMS suite, with no Laravel match.
  • Nobody on the team will own Composer updates, deploys and server cron.
  • You need a huge theme marketplace. Laravel's ecosystem is strong for code, but smaller for ready-made themes.
And Lara Dashboard is not the right base for every Laravel project.
  • You only need staff screens over your own models. Filament is lighter.
  • You want content as flat files in Git. Statamic does that well.
  • You need translated front-end content in core today. The admin is translated, but content translation needs extra work.
  • Your hosting is stuck below PHP 8.3.

Self-check: are you thinking in Laravel yet?

Try these on your next feature.
  1. Where will this data live: its own table with a migration, or a post type?
  2. Which fields need real columns because you filter or sort by them?
  3. Who can see and change it, and which policy checks that?
  4. Does anything run on a timer, and is it in the scheduler with a server cron?
  5. Is slow work pushed to a queue instead of the request?
  6. Are secrets in .env and out of the database and Git?
  7. Is the feature a module or package you can switch off?
  8. Do you have a test for the permission rule?
When you move a live site, plan redirects and metadata early. Our WordPress to Laravel migration checklist covers content, SEO, auth and media.

Verdict

Going from WordPress to Laravel is a change of structure, not of skills. You already know hooks, content types, roles and scheduled jobs. Laravel gives each one a clearer home, with typed models, versioned migrations and real cron. The gap is the CMS layer that WordPress gives you for free. If you want that layer, with WordPress-style helpers and hooks, in an MIT Laravel app, try Lara Dashboard and see how much feels familiar.

FAQ

Is Laravel harder to learn than WordPress?

For PHP developers, the language is the same. The harder part is the structure: models, migrations, providers and Composer. It gets much easier once you map each WordPress idea to its Laravel home, as in this post.

Does Laravel have plugins like WordPress?

Laravel uses Composer packages, which you install from Packagist. There is no built-in admin screen to activate them. Lara Dashboard adds modules that you can switch on and off in the admin or upload as a ZIP.

Can I use add_action and add_filter in Laravel?

Not natively. Laravel uses events and listeners. Packages such as Eventy add WordPress-style actions and filters, and Lara Dashboard wraps Eventy in ld_add_action and ld_add_filter helpers with enum hook names.

What replaces custom post types in Laravel?

Usually an Eloquent model with its own table. For editorial content, Lara Dashboard also supports register_post_type and register_taxonomy, so you get admin screens without new migrations.

What is the Laravel version of WP-CLI?

Artisan. It runs migrations, clears caches, creates classes and runs your own commands. You start it with php artisan in the project folder.
Laravel CMS Open source Module Architecture WordPress

Try Lara Dashboard for Free

Explore every feature live — no sign-up required.

Launch Live Demo