mmintel/klz-cables.com

Fork 0

Files

Marc Mintel c2d6e082e8

Build & Deploy KLZ Cables / deploy (push) Successful in 3m50s

Details

umami migration

2026-01-25 11:23:34 +01:00

6.5 KiB

Raw Blame History

Migrating Analytics from Independent Analytics to Umami

This guide explains how to migrate your analytics data from the Independent Analytics WordPress plugin to Umami.

What You Have

You have exported your analytics data from Independent Analytics:

data/pages(1).csv - Page-level analytics data with:
- Title, Visitors, Views, View Duration, Bounce Rate, URL, Page Type
- 220 pages with historical data

What You Need

Before migrating, you need:

Umami instance running (self-hosted or cloud)
Website ID from Umami (create a new website in Umami dashboard)
Access credentials for Umami (API key or database access)

Migration Options

The migration script provides three output formats:

Option 1: JSON Import (Recommended for API)

python3 scripts/migrate-analytics-to-umami.py \
  --input data/pages\(1\).csv \
  --output data/umami-import.json \
  --format json \
  --site-id YOUR_UMAMI_SITE_ID

Import via API:

curl -X POST \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d @data/umami-import.json \
  https://your-umami-instance.com/api/import

Option 2: SQL Import (Direct Database)

python3 scripts/migrate-analytics-to-umami.py \
  --input data/pages\(1\).csv \
  --output data/umami-import.sql \
  --format sql \
  --site-id YOUR_UMAMI_SITE_ID

Import via PostgreSQL:

psql -U umami -d umami -f data/umami-import.sql

Option 3: API Payload (Manual Import)

python3 scripts/migrate-analytics-to-umami.py \
  --input data/pages\(1\).csv \
  --output data/umami-import-api.json \
  --format api \
  --site-id YOUR_UMAMI_SITE_ID

Step-by-Step Migration Guide

1. Prepare Your Umami Instance

If self-hosting:

# Clone Umami
git clone https://github.com/umami-software/umami.git
cd umami

# Install dependencies
npm install

# Set up environment
cp .env.example .env
# Edit .env with your database credentials

# Run migrations
npm run migrate

# Start the server
npm run build
npm run start

If using Umami Cloud:

Sign up at https://umami.is
Create a new website
Get your Website ID from the dashboard

2. Run the Migration Script

Choose one of the migration options above based on your needs.

Example:

# Make the script executable
chmod +x scripts/migrate-analytics-to-umami.py

# Run the migration
python3 scripts/migrate-analytics-to-umami.py \
  --input data/pages\(1\).csv \
  --output data/umami-import.json \
  --format json \
  --site-id klz-cables

3. Import the Data

Option A: Using Umami API (Recommended)

Get your API key:
- Go to Umami dashboard → Settings → API Keys
- Create a new API key

Import the data:

curl -X POST \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d @data/umami-import.json \
  https://your-umami-instance.com/api/import

Option B: Direct Database Import

Connect to your Umami database:
```
psql -U umami -d umami
```

Import the SQL file:

psql -U umami -d umami -f data/umami-import.sql

Verify the import:

SELECT COUNT(*) FROM website_event WHERE website_id = 'klz-cables';

4. Verify the Migration

Check Umami dashboard:
- Log into Umami
- Select your website
- View the analytics dashboard
Verify data:
- Check page views count
- Verify top pages
- Check visitor counts

Important Notes

Data Limitations

The CSV export from Independent Analytics contains aggregated data, not raw event data:

✅ Page views (total counts)
✅ Visitor counts
✅ Average view duration
❌ Individual user sessions
❌ Real-time data
❌ Geographic data
❌ Referrer data
❌ Device/browser data

What Gets Imported

The migration script creates simulated historical data:

Each page view becomes a separate event
Timestamps are set to current time (for historical data, you'd need to adjust)
Duration is preserved from the average view duration
No session tracking (each view is independent)

Recommendations

Start fresh with Umami:
- Let Umami collect new data going forward
- Use the migrated data for historical reference only
Keep the original CSV:
- Store data/pages(1).csv as a backup
- You can re-import if needed
Update your website:
- Replace Independent Analytics tracking code with Umami tracking code
- Test that Umami is collecting new data
Monitor for a few days:
- Verify Umami is collecting data correctly
- Compare with any remaining Independent Analytics data

Troubleshooting

Issue: "ModuleNotFoundError: No module named 'csv'"

Solution: Ensure Python 3 is installed:

python3 --version
# Should be 3.7 or higher

Issue: "Permission denied" when running script

Solution: Make the script executable:

chmod +x scripts/migrate-analytics-to-umami.py

Issue: API import fails

Solution: Check:

API key is correct and has import permissions
Website ID exists in Umami
Umami instance is accessible
JSON format is valid

Issue: SQL import fails