Weave Code
Laravel Crm Laravel Package
venturedrake/laravel-crm
Laravel CRM is a free, open-source, self-hosted CRM package for Laravel applications. It provides leads, contacts, accounts, deals, activities, notes, and customizable sales pipelines, plus modern Laravel authentication and Blade UI components to help you add CRM functionality quickly and easily.
VentureDrake Laravel CRM is an open-source CRM package that drops a complete customer-management module into any Laravel application. It ships with ready-made models, migrations, routes, controllers, and Blade views, so you can manage leads, contacts, and sales pipelines without building the foundation yourself. The included web UI is themeable and integrates cleanly with existing Laravel auth, making it straightforward to extend or embed.
- Leads & contacts — track prospects, convert them to customers, and log every interaction.
- Deals pipeline — organize opportunities with stages, values, and expected close dates.
- Activities & tasks — attach notes and to-dos to any record for full history.
- Custom fields — extend built-in entities without touching core migrations.
- REST API & policies — consume CRM data programmatically with Laravel-native authorization.
Frequently asked questions about Laravel Crm
- How do I install VentureDrake Laravel CRM via Composer?
- Install it with Composer using composer require venturedrake/laravel-crm. The package uses Laravel auto-discovery for its service provider; publish the config/package.php configuration and any assets, run the migrations, then run php artisan laravelcrm:update to seed settings and mark the database version. Verify the settings middleware and Livewire are available in the host app before opening the admin UI.
- Which Laravel versions does laravel-crm support?
- The baseline assumes a Laravel application on a currently supported major, specifically Laravel 10, 11, or 12, with Livewire for the form layer. Because support is declared in the package's composer.json, check that file and the release notes for the exact constraint before upgrading. The 2.4.7 patch introduces no new dependencies, so it should not change your Laravel or PHP constraints.
- Do I need Livewire to use this Laravel CRM package?
- Yes. The package ships Livewire components for contact and organization entry, so the host application must already use Livewire. Confirm the required Livewire major version in composer.json and test the trait-based suggest/autocomplete hooks against that release, since the 2.4.7 fix lives inside two Livewire traits.
- How do I add custom fields to leads, contacts, or deals in laravel-crm?
- Laravel CRM includes customizable fields so you can extend leads, contacts, organizations, deals, quotes, and tasks without altering the package schema. Configure the fields through the admin UI or the package configuration, then clear cached settings so the new fields appear. Test the field definitions against your encrypted-field settings if you use encrypt_db_fields.
- Does laravel-crm include roles and permissions?
- Yes, the package includes roles and permissions for controlling access to CRM records and admin functions. Assign roles to users in the host application and verify that the settings middleware resolves the correct permissions. Review the default policies after installation to match your application's authorization model.
- Is there a REST API for leads, contacts, deals, quotes, and tasks?
- Yes. The package exposes a REST API for managing leads, contacts, organizations, deals, quotes, and tasks alongside the admin UI. Authenticate API requests using your application's guard or token strategy and confirm route prefixes in the published configuration. The 2.4.7 patch does not change the API surface, so existing integrations should continue to work.
- How does encrypt_db_fields work with laravel-crm?
- Laravel CRM supports encrypted database fields through the encrypt_db_fields setting. When encryption is enabled, the suggest/autocomplete traits are expected to compare against decrypted model values; the 2.4.7 fix updates that behavior in two Livewire traits. Test name-matching and link-clearing behavior with encryption on, because encrypted values cannot be compared directly at the database level.
- Is it safe to upgrade to laravel-crm 2.4.7?
- The 2.4.7 release is a patch with no schema change, no new dependencies, and no API surface change. It corrects a config constant and fixes a real defect where editing a linked person's name left a stale person_id or organization_id, which could attach the wrong record on save. Upgrading requires no host-application code changes, but users may notice that a non-matching edited name clears the existing link and requires them to re-pick it.
- Why does laravel-crm report the wrong version or say the database is behind?
- The package duplicates its version identity across config/package.php, SystemCheckService::normalisedVersion(), the db_version marker written by laravelcrm:update, the UpdateController banner, and a version-keyed middleware cache flag. If a release ships with a stale version constant, the update banner and the database-is-behind check can misreport, and the version-keyed seeding flag may silently suppress a re-seed. Run php artisan laravelcrm:update after upgrading and compare config('package.version') with the installed release; ideally add a CI check that asserts that value matches your latest git tag or composer.json.
- What are alternatives to venturedrake/laravel-crm?
- Alternatives include other Laravel CRM packages and building a custom CRM on Laravel models, policies, and Livewire forms. Evaluate each option on maintained Laravel version support, Livewire compatibility, REST API coverage, custom fields, and encrypted-field handling. Because laravel-crm's version constant is manually maintained and not evidently guarded by a build check, review its release cadence and changelog before committing in production.
Weaver
How can I help you explore Laravel packages today?