Skip to main content

Upgrading and Migrating DreamFactory

Current Version & Changelog

The current stable release of DreamFactory is v7.x. For the full list of releases, version history, and release notes, see the DreamFactory GitHub Releases page.

Each release includes a changelog describing new features, bug fixes, and any breaking changes. Before upgrading, review the changelog for your target version to identify any actions required on your end (e.g., PHP version changes, .env configuration additions, or deprecated API behaviors).

To check the version currently running on your instance, log in to the DreamFactory admin panel and navigate to Admin > About DreamFactory, or run:

php artisan df:version

Upgrade Path by Version

Use the table below to identify the appropriate upgrade method based on your current and target versions:

From VersionTo VersionMethodNotes
4.x5.xIn-place (git pull)PHP 7.4+ required; run php artisan migrate --seed
5.x6.xIn-place (git pull)Review .env for new required variables; check deprecated connectors
6.x7.xIn-place or fresh migrationPHP 8.1+ required; significant dependency updates — test in staging first
AnyCross-serverFull migration (see below)Use the Major Version Migration process to copy .env and system database

Breaking changes to watch for:

  • 3.x → 4.x: System database schema changed significantly — a fresh migration is required; data can be re-imported via the 4.x import tools.
  • 5.x → 6.x: Several legacy connectors were removed; verify your active services are still supported.
  • 6.x → 7.x: PHP minimum version bumped to 8.1; Composer 2 required; some deprecated API behaviors removed.

Pre-Upgrade Checklist

Before starting any upgrade, complete these steps to ensure you can recover if something goes wrong:

  1. Back up the .env file — this file contains your APP_KEY, database credentials, and all environment-specific configuration. Without it, encrypted data is unrecoverable.

    cp /opt/dreamfactory/.env /opt/dreamfactory/.env.backup.$(date +%Y%m%d)
  2. Back up the system database — the system database stores all your API configurations, roles, scripts, and user accounts. Use the Step 2: Back Up the System Database instructions below for your database type.

  3. Note your PHP version — confirm the target DreamFactory version supports your current PHP installation:

    php --version
  4. Note custom scripts and connectors — list any event scripts, scripted services, or custom connectors you've added so you can verify they still function after the upgrade.

  5. Check scheduled jobs and cron tasks — if you use DreamFactory's scheduler or have external cron jobs calling DreamFactory APIs, document them before upgrading.

  6. Test in a staging environment first — if possible, clone your instance to a staging server and run the upgrade there before applying it to production.

Rolling Back an Upgrade

If an upgrade fails or causes unexpected behavior, restore your previous state using the backups created in the Pre-Upgrade Checklist:

Step 1: Restore the application files

If you performed an in-place upgrade via git pull, revert to the previous commit:

cd /opt/dreamfactory
git log --oneline -5 # identify the commit hash before the upgrade
git checkout <previous-commit-hash>
composer install --no-dev --ignore-platform-reqs

If you made a file-based backup (cp -r dreamfactory dreamfactory.backup), restore it:

cp -r /opt/dreamfactory.backup /opt/dreamfactory

Step 2: Restore the system database

Use your database-specific method to restore the dump.sql backup:

# MySQL example
mysql -u root -p dreamfactory < /path/to/dump.sql

# PostgreSQL example
psql -U root -d dreamfactory < /path/to/dump.sql

Step 3: Restore the .env file

cp /opt/dreamfactory/.env.backup.YYYYMMDD /opt/dreamfactory/.env

Step 4: Clear caches and restart

php artisan cache:clear
php artisan config:clear
sudo systemctl restart nginx

After restoring, verify the admin panel loads correctly and your APIs respond as expected.


This guide covers two different scenarios for updating your DreamFactory installation:

  • Minor Version Upgrades: In-place updates for patch releases and minor versions (e.g., 7.0.0 → 7.1.0)
  • Major Version Migration: Complete migration to a new server or environment, typically for major version changes or infrastructure updates

Choose the appropriate section based on your needs. Most users will use the minor version upgrade process for routine updates.


Minor Version Upgrades

For minor version upgrades and patch releases, you can perform an in-place upgrade of your existing DreamFactory installation. This process uses Git, Composer, and Laravel's Artisan commands to update your current environment.

Prerequisites

  • Backup Required: Always perform complete backups before upgrading
  • Git Repository: Your DreamFactory installation must be a Git repository
  • Command Line Access: Shell/SSH access to your server
  • Permissions: Proper file permissions on storage and cache directories

Upgrade Process

Step 1: Create Backups

Navigate to one level above your DreamFactory directory (typically /opt/dreamfactory) and create a file backup:

cd /opt
cp -r dreamfactory dreamfactory.backup

Create a database backup, reference for methods found here.

Step 2: Prepare for Upgrade

Navigate to your DreamFactory installation directory:

cd /opt/dreamfactory

Stash any local changes to preserve modifications:

git stash

Step 3: Update Source Code

Switch to the master branch:

git checkout master

Pull the latest version:

git pull origin master

Step 4: Update Dependencies and Permissions

Set proper permissions on cache directories. Replace {web-service-user} with your web server user (e.g., www-data, dreamfactory) and {your-user-group} with your user group:

sudo chown -R {web-service-user}:{your-user-group} storage/ bootstrap/cache/

e.g., sudo chown -R dreamfactory:dreamfactory storage/ bootstrap/cache/

sudo chmod -R 2775 storage/ bootstrap/cache/

Update Composer dependencies:

composer install --no-dev --ignore-platform-reqs

Run database migrations:

php artisan migrate --seed

Clear application cache and config:

php artisan cache:clear
php artisan config:clear

Step 5: Restart Web Server

For Nginx (DreamFactory default)

sudo systemctl restart nginx

For Apache:

sudo systemctl restart apache2

Troubleshooting

Composer Install Errors

Clear Composer cache:

composer clear-cache

Remove vendor directory and reinstall:

rm -rf vendor/
composer install --no-dev --ignore-platform-reqs

Permission Issues

Reset permissions on critical directories:

sudo chown -R {web-service-user}:{your-user-group} storage/ bootstrap/cache/

e.g., sudo chown -R dreamfactory:dreamfactory storage/ bootstrap/cache/

sudo chmod -R 2775 storage/ bootstrap/cache/

Migration Command Not Found

Clear compiled cache files:

rm -rf bootstrap/cache/compiled.php storage/framework/cache/*

Retry the composer install:

composer install --no-dev --ignore-platform-reqs

Verification

After completing the upgrade:

  1. Check DreamFactory version in the admin interface
  2. Test your APIs to ensure they're functioning correctly
  3. Verify user access and permissions are intact
  4. Check system logs for any errors

Major Version Migration

For major version changes or when migrating to a new server/environment, you'll need to migrate your DreamFactory instance completely. This process focuses on transferring two critical components: the .env file and the DreamFactory system database.

Why These Components Matter

.env File

Contains essential configuration settings including:

  • The APP_KEY (critical for data encryption)
  • Database credentials
  • Caching preferences
  • API keys
  • Environmental settings

DreamFactory System Database

Stores all your configuration data:

  • User accounts
  • Scripts
  • API configurations
  • System-level metadata

Migrating these components ensures your new instance contains all original configurations, eliminating manual recreation.

File Transfer Reference

CLI File Transfer Methods by Deployment Type

FROM remote TO local

scp <user>@<remote-server>:/path/to/file local-destination/

Example: scp root@192.168.1.100:/opt/dreamfactory/.env .

FROM local TO remote

scp local-source <user>@<remote-server>:/path/to/destination/

Example: scp dump.sql root@192.168.1.100:/opt/dreamfactory/

Migration Process

Step 1: Back Up the .env File

Navigate to the DreamFactory root directory:

cd /opt/dreamfactory

Copy the .env file to your local machine (see File Transfer Reference for deployment-specific commands):

scp <user>@<remote-server>:/opt/dreamfactory/.env .

Tip: Store the .env file in a secure location to recover from any migration issues.

Step 2: Back Up the System Database

Use the system database credentials from the .env file to create a backup:

Backup Methods by Database Type
mysqldump -u root -p --databases dreamfactory --no-create-db > dump.sql

Replace root with your database user and dreamfactory with your database name if different.

Transfer the backup file to a secure external location:

scp <user>@<remote-server>:/opt/dreamfactory/dump.sql .

Step 3: Prepare the New DreamFactory Instance

  1. Set up a new server with a clean operating system installation
  2. Follow the DreamFactory installation guide for your platform
  3. Complete the initial setup by creating an administrator account (this will be replaced with migrated data)

Step 4: Additional Configuration

MySQL Specific Configuration

If upgrading MySQL versions (e.g., 5.6 to 5.7+), you may need to disable strict mode by opening config/database.php and adding 'strict' => false under the MySQL configuration section.

General Configuration

Ensure all system dependencies are up to date. DreamFactory supports PHP 8.1 or later.

Step 5: Import the System Database

Transfer the dump.sql file to the new server:

scp dump.sql <user>@<new-server>:/opt/dreamfactory/

Clear the default database schema:

php artisan migrate:fresh
php artisan migrate:reset

Import the database backup:

Import Methods by Database Type
mysql -u root -p dreamfactory < dump.sql

Run database migrations to apply schema updates:

php artisan migrate --seed

Edit the .env file and replace the APP_KEY with the value from your old instance:

APP_KEY=YOUR_OLD_APP_KEY_VALUE

Clear caches to finalize the configuration:

php artisan cache:clear
php artisan config:clear

Migration Verification

Log in to the new DreamFactory instance using credentials from the migrated environment. Verify that:

  1. All user accounts are present and accessible
  2. API configurations are intact
  3. Scripts and custom logic are functioning
  4. Database connections work properly
  5. System settings match your original configuration

Congratulations! Your DreamFactory instance has been successfully migrated.