Introduction
Managing data effectively is key to getting the most out of your Qomon space. This article explains why database size matters, what happens with larger datasets, and the best practices to ensure your team enjoys a smoother user experience.
Why Database Size Matters
Database size can impact how quickly and smoothly your team can access, view, and work with data - affecting things from loading times and map display to device performance, costs, and even environmental impact.
Keeping it below a certain size can mean:
Faster loading times - Your team can access data quicker
Smoother user experience - No browser lag or performance hiccups
Better machine performance - Keeps your devices running efficiently
Cost optimization - Reduces resource consumption and associated costs
Save the planet - Resources consumption
Instant map display - Contacts appear on the map automatically
Immediate access - Contacts are available after filtering
Optimal Recommendation:
< 10-15 million contacts per space.
We recommend keeping your database to under 10 to 15 million contacts per space for optimal performance. This isn’t a hard limitation - just our recommendation for the best user experience.
💡 Tip: With our Expert 2 plan, you can benefit from multiple spaces (child spaces) that are connected to a Central Space (parent space).
Having more than 15 million in one Qomon space:
The platform adapts when you upload larger files with some trade-offs:
Performance Adjustments:
Map display: Contacts won’t automatically appear on the map - you’ll need to apply filters first
Contact lists: The full contacts list won’t preload - filters are required before data displays
Loading behavior: The system prioritizes stability over immediate access to all data.
Best Practices Before Uploading:
Audit your data - Remove outdated or irrelevant contacts
Segment strategically - Consider splitting large datasets by geography, demographics, or priorities. Sometimes a full voter file isn't necessary if you're only focusing on specific areas.
Clean your lists - Remove duplicates and invalid entries
Prioritize active contacts - Focus on engaged supporters, priority 1 and 2 supporters, voters, donors, constituents, etc.
For Large Datasets
If you need to upload comprehensive files:
Plan for filter usage - Train your team to use filters effectively
Consider phased uploads - Start with priority segments, add others as needed
Test performance - Upload a sample first to gauge system response
Communicate with your team - Let users know they’ll need to filter before viewing data
Commonly asked question:
“Should we import the entire voter file?”
This depends on your campaign strategy:
✅ Yes, if:
You’re running a comprehensive voter contact program.
Your team is comfortable working with filtered datasets.
You want all data available in one central place.
⚠️ Consider alternatives, if:
You’re focused only on specific voter segments.
You need immediate, unfiltered access to contact lists.
You’re already experiencing performance issues.
You prefer to minimize platform resource usage.
Need Help?
If you’re unsure about the best approach for your specific dataset or campaign needs, contact our support team.