Upgrade Version

Upgrades should be handled as production deployments. Back up first, update the main product before addons, run migrations, clear cache, and test critical buyer workflows before sending traffic back to the application.

Marketplace Update Workflow

Open the Marketplace or Packages area and check for available updates. Package sources may include marketplace downloads, Envato purchase flow, uploaded ZIP files, or vendor-provided addon archives. Confirm the update belongs to LeadFlow AI and is compatible with the installed version.

Backup Before Update

Back up the database.
Back up the application files, especially .env, storage, uploads, and custom assets.
Record installed addon versions and enabled modules.
Export important leads or reports when the update affects lead, funnel, or reporting tables.

Update Order

Put the application into maintenance mode when updating production.
Update the main LeadFlow AI product first.
Run migrations for the core product.
Update addon packages such as AI, automations, reports, marketplace tools, or integrations.
Run addon migrations and seeders if the addon requires them.
Run cache clearing and optimized autoload steps.

Manual ZIP Update

When using a ZIP package, extract it locally, compare the package structure, upload the new files, and do not overwrite .env or storage uploads. If the package includes a modules directory, update only the addon module folders that belong to the installed packages. Run composer dump-autoload -o if PHP classes were added, then run migrations and clear cache.

Post-update Checks

Login as admin and normal user.
Open /docs/leadflow-ai and confirm documentation still loads.
Create a test form, publish it, submit it, and verify the response and lead record.
Open a funnel and confirm public pages, redirects, and thank-you behavior.
Check surveys, QR redirects, share links, embed codes, files, custom domains, automations, webhooks, emails, analytics, payments, and marketplace package list.

Troubleshooting Update Problems

If routes fail, clear route/config/view cache. If new classes are missing, dump optimized autoload. If a page references an addon that is not installed, disable the plan permission or install the addon. If migrations fail, restore the backup and inspect the failing migration before retrying. If public forms stop recording leads, check database migrations, queue workers, captcha, spam settings, and webhook errors.

Buyer Readiness Notes

Before using Upgrade Version in production, confirm that the application has been installed on the correct licensed domain, cache has been cleared after configuration changes, and all relevant workspace permissions have been tested with realistic user accounts. LeadFlow AI is often used as a customer-facing SaaS product, so a setting that looks internal during setup can affect paid users, published forms, funnel redirects, lead records, invoices, files, domains, or addon visibility.

For agency deployments, prepare a repeatable launch checklist for each workspace. The checklist should include workspace branding, form fields, consent copy, funnel pages, tracking fields, notification recipients, lead assignment rules, reports, file storage, custom domains, support ownership, and team permissions. For SaaS deployments, prepare a platform checklist that covers plans, payment gateways, mail delivery, queue workers, cron, file storage, AI provider settings, marketplace packages, backups, privacy pages, and production debug mode.

When troubleshooting this area, separate configuration problems from data problems. Configuration problems usually involve cache, plan permissions, missing addons, provider credentials, mail settings, queue workers, or route discovery. Data problems usually involve workspace ownership, hidden fields, duplicate slugs, invalid imports, deleted parent records, old embed codes, or team permission rules. Testing with a fresh private browser session and a non-admin account helps confirm the real customer experience.

Operational FAQ

Who should review this page?
Product owners, SaaS admins, agency operators, support staff, and implementation partners should review it before changing related production workflows.

What should be documented internally?
Record any custom domain rules, installed addons, plan limits, payment provider settings, AI provider settings, integration credentials, and client-specific visibility decisions.

What is the safest production habit?
Back up first, change one thing at a time, clear cache when the change affects Laravel configuration or package discovery, then test the exact user or client workflow that depends on the change.