Migration from Beta

This guide explains how to migrate from Fusionaly Beta to the current versions: Free (open source) and Pro.

What’s Changed in v1

• Free edition - The core analytics is now open source under AGPL-3.0
• Pro edition - Adds Ask AI, Lens, public dashboards, and email support
• New Docker images - fusionaly-oss (Free) and fusionaly-pro (Pro)
• Same data format - Your existing database is fully compatible

Before You Start

1. Back up your database - Always back up before major upgrades
2. Note your current settings - Check your .env file or Docker environment variables
3. Choose your edition - Decide between Free and Pro

Migration Steps

If Using Fusionaly Manager

If you installed using the automated installer:

# 1. Back up your database (the manager does this automatically, but be safe)
sqlite3 /opt/fusionaly/storage/fusionaly-production.db ".backup /opt/fusionaly/backup-before-v1.db"

# 2. Upgrade to Pro (if you have a license)
fusionaly upgrade

The upgrade command will switch to the Pro Docker image and restart containers. Visit your dashboard after to enter your license key.

If Using Docker Directly

If you’re running Docker manually or with docker-compose:

# 1. Back up your database
docker exec fusionaly sqlite3 /app/storage/fusionaly-production.db ".backup /app/storage/backup-before-v1.db"

# Or if using a volume mount:
sqlite3 /path/to/your/storage/fusionaly-production.db ".backup /path/to/backup-before-v1.db"

# 2. Pull the new image
docker pull karloscodes/fusionaly-oss:latest   # For Free
# or
docker pull karloscodes/fusionaly-pro:latest   # For Pro

# 3. Stop the old container
docker stop fusionaly
docker rm fusionaly

# 4. Start with the new image
docker run -d \
  --name fusionaly \
  -p 8080:8080 \
  -e FUSIONALY_LICENSE_KEY="your-license-key" \  # Only needed for Pro
  -e FUSIONALY_DOMAIN="your-domain.com" \
  -e FUSIONALY_PRIVATE_KEY="your-existing-private-key" \
  -v fusionaly-storage:/app/storage \
  -v fusionaly-logs:/app/logs \
  karloscodes/fusionaly-oss:latest  # or fusionaly-pro:latest

If Using Docker Compose

Update your docker-compose.yml:

services:
  fusionaly:
    image: karloscodes/fusionaly-oss:latest  # or fusionaly-pro:latest
    # ... rest of your config stays the same

Then:

docker compose pull
docker compose up -d

Environment Variables

The environment variables are the same between Beta and v1:

Variable	Required	Description
FUSIONALY_DOMAIN	Yes	Your domain name
FUSIONALY_PRIVATE_KEY	Yes	Encryption key (keep the same!)
FUSIONALY_LICENSE_KEY	Pro only	Your Pro license key
FUSIONALY_APP_PORT	No	Port (default: 8080)
FUSIONALY_LOG_LEVEL	No	debug, info, warn, error

Caution

Important: Use the same FUSIONALY_PRIVATE_KEY as your previous installation. Changing this will break session tracking.

Verifying the Migration

After starting the new container:

1. Check the logs:

   docker logs fusionaly

2. Access your dashboard - Visit your domain and log in

3. Verify data - Check that your historical analytics data is visible

4. Test tracking - Visit a tracked site and verify new events appear

Troubleshooting

”License key required” error (Pro only)

Make sure FUSIONALY_LICENSE_KEY is set in your environment variables.

Data not showing

Ensure you’re using the same storage volume/path as before. The database file should be at /app/storage/fusionaly-production.db inside the container.

Session tracking broken

You may have changed the FUSIONALY_PRIVATE_KEY. Restore your original key from your backup or .env file.

Rollback

If something goes wrong, you can roll back to Beta:

# Stop the new container
docker stop fusionaly
docker rm fusionaly

# Restore your database backup if needed
cp /path/to/backup-before-v1.db /path/to/storage/fusionaly-production.db

# Start the old Beta image
docker run -d \
  --name fusionaly \
  ... \
  karloscodes/fusionaly-beta:latest

Getting Help

• Free edition: GitHub Issues
• Pro edition: Email support (check your license email for details)