Data Import

The data import feature allows you to migrate your historical analytics data from other platforms to Rybbit. This preserves your analytics history when switching from competitors, giving you a complete view of your data without losing valuable insights.

Supported Platforms

Currently, Rybbit supports importing data from:

• Umami
• Simple Analytics
• Plausible

Additional platforms may be added in the future based on user demand.

Plan Requirements

Cloud Version

Self-Hosted Version

Self-hosted installations have unlimited access to data imports with no restrictions on:

• Historical data window (import data from any date)
• Event quotas (no monthly limits)
• Concurrent imports (no limit on active imports)

Import Limits

Historical Data Windows

The historical data window determines how far back you can import data:

• Standard plans: Import data from the past 24 months (2 years)
• Pro plans: Import data from the past 60 months (5 years)
• Self-hosted: Unlimited - import data from any date

Events outside your plan's historical window will be automatically skipped during import.

Event Quotas

Each imported event counts against the calendar month it happened in, not the month you run the import. Every month can hold up to your plan's monthly event limit, including the events Rybbit already tracked for your organization that month and anything imported earlier:

• Events that would push their month over the limit are skipped
• Skipped events are counted and displayed in the import history
• Importing older data doesn't use up the current month's quota; only events dated this month count toward it
• If a month in your source data is busier than your plan allows, upgrade to a plan with a higher event limit before importing

Concurrent Imports

For cloud users:

• Maximum 1 active import per organization
• New imports are blocked until the current one completes
• An import that hasn't finished after 2 hours is marked Failed and no longer blocks new imports

Self-hosted users have no concurrent import restrictions.

How to Import Data

Import History

The Import History section displays all your past and current imports.

Import Metrics

Each import shows three key metrics:

Imported Events

• Number of events successfully imported into Rybbit
• These events are now visible in your analytics dashboard

Skipped Events

• Events that were excluded during import
• Common reasons:
  • Outside your plan's historical data window
  • Would push the month they happened in over your plan's monthly event limit

Invalid Events

• Events that failed validation during import
• Common reasons:
  • Malformed CSV data
  • Missing required fields
  • Invalid date/time formats
  • Data type mismatches

Managing Imports

Deleting Imports

• Click the trash icon next to any completed or failed import
• Confirm the deletion in the dialog
• This will permanently remove the import record and all associated events from your analytics
• Active imports cannot be deleted

Troubleshooting

Events Skipped Due to Quota Limits

Cause: The months those events happened in already reached your plan's monthly event limit, counting the events Rybbit tracked then and earlier imports.

Solution:

• Upgrade to a plan with a higher monthly event limit
• After upgrading, delete the import, then import the whole file again. Importing it again without deleting stores the events it already imported twice
• Start the new import at least 2 hours after the original one finished. Until then its events still count against your limit, even after you delete it
• Waiting for the next billing cycle doesn't help: imported events count against the months they happened in, and past months don't reset

Events Skipped Due to Date Range

Cause: Events are older than your plan's historical data window.

Solution:

• Upgrade to Pro plan for 60-month history (vs 24-month on Standard)
• For self-hosted, no action needed - all dates are allowed
• Filter your CSV export to only include recent data

High Invalid Event Count

Cause: CSV format doesn't match the expected structure for your platform.

Solution:

1. Verify you selected the correct platform
2. Check that your CSV export includes all required fields
3. Look for special characters or malformed data in the CSV
4. Try importing a small sample file (first 100 rows) to test

Import Appears Stuck

Cause: Very large files take time to upload, or the browser tab was closed or lost its connection before the upload finished.

Solution:

• Keep the tab open while a large file uploads
• An import that hasn't finished after 2 hours is marked Failed, and you can start a new one
• Events imported before it stopped stay in your analytics. Delete the failed import to remove them before importing the file again
• Contact support if no events were imported

Best Practices

Before You Import

1. Export a complete backup from your current analytics platform
2. Test with a small sample (first 1,000 rows) before importing your full dataset
3. Check each month in your source data against your monthly event limit, minus what Rybbit already tracked or imported that month
4. Verify date ranges match your plan's historical window
5. Review CSV format matches the required structure for your platform

During Import

1. Don't close the browser tab
2. Monitor the progress in the Import History section
3. Check for skipped/invalid events early to catch format issues
4. Wait for completion before starting another import (cloud users)

After Import

1. Verify your data appears correctly in analytics dashboards
2. Check date ranges to ensure historical data is visible
3. Compare totals with your source platform to validate accuracy
4. Keep the original CSV as a backup before deleting the import