Importing past data into Church Metrics using a CSV file can save time, but the importer is very strict. Even small formatting errors or mismatches will cause the upload to fail. This guide covers the most common errors, what they mean, and how to fix them.
❌ Common Import Errors & Fixes
1. Service Time Wasn’t Found on Row X
This error means the Service Date/Time in your CSV doesn’t match a service time in your account.
Possible causes:
Wrong day of the week (e.g., Monday instead of Sunday).
Wrong date format.
Entered a value in Service Time ID (should be blank).
Specified an Event Name without creating that Event first.
Tried saving a special service (e.g., Christmas Eve) without defining a matching Event Service Time.
Fix:
Confirm your Service Date Time matches an active service time in Admin → Service Times.
Use the correct format:
US:
M/D/YYYY HH:MM AM/PM→ Example:1/5/2025 10:00 AMInternational:
YYYY-MM-DD HH:MM→ Example:2025-01-05 14:00
Leave Service Time ID blank unless re-importing exported data.
If importing to an Event, make sure Event and Event Service Times exist.
👉 Note: Importer row numbers do not include the header row. If the error says “Row 65,” it’s actually line 66 in your file.
2. Invalid Header
This means your file headers don’t match the required format.
Fix:
Make sure your file is saved as a
.csv(comma-separated file).Always start with the official sample CSV template from Church Metrics.
Do not rename, delete, or reorder headers. Even unused columns must remain.
3. Service Date & Time Format Issues
Every row must include both a date and a time.
✅ Correct: 1/5/2025 10:00:00 AM
❌ Incorrect: 1/5/2025 or Good Friday
Fix:
Enter both date and time.
For afternoon services, use 24-hour format (e.g.,
1/5/2025 14:00).
4. Category or Campus Name Mismatches
If a category or campus name doesn’t match exactly, the row will fail.
Common mistakes:
Extra/missing spaces (e.g.,
Attendance-Youthvs.Attendance - Youth).Different punctuation (
&vs.and).Outdated names.
Importing into a Parent Category instead of a subcategory.
Fix:
Compare names in your CSV to Admin → Categories and Admin → Campuses.
Correct spelling, punctuation, and spacing.
Only import to actual categories, not parents.
5. Value Formatting Errors
Values must be plain numbers.
✅ Correct: 100000 or 692.54
❌ Incorrect: $100,000 or 1,000.00
6. Event Name Issues
The Event Name column is only needed if the data is tied to a specific Event.
Fix:
Leave blank for regular service times.
If importing Event data, confirm the Event exists and Event Service Times are created.
7. “Other” Field Issues
The Other column is a special field for midweek or unscheduled services.
Fix:
Leave blank unless you intend to assign the entry to “Other.”
If used, enter
Yesin this column. The Service Date Time will then be ignored.
8. Large File Errors / Timeouts
Imports with too many records may time out.
Fix:
Break files into smaller imports (e.g., by campus or category).
Keep files under 500 rows per upload for faster processing.
📑 CSV File Column Definitions
Column | Description |
Campus Slug | Campus name. Must exactly match an existing campus. |
Category Name | Category name. Must match exactly. Do not import to Parent Categories. |
Value | Attendance number (integer) or giving number (up to 2 decimals). No symbols or commas. |
Service Date Time | Full date and time. US or International format accepted. |
Event Name | Only use if data belongs to an existing Event. |
Other | Optional. Enter “Yes” to assign to the default “Other” service time, thus ignoring set service times. |
Service Time ID | Internal field used for re-importing exported data. Leave blank unless needed. |
📝 Best Practices for Import Success
Always use the official sample CSV.
Keep all headers, even if you’re not using them.
Use Excel’s TRIM() function to remove hidden spaces.
Test with a small file first before uploading large batches.
Import tricky data (like Events or Offerings) separately.
🙋 Still Stuck?
If your file won’t import after trying the above:
Re-check Service Date Time formatting.
Confirm names match exactly in Campuses and Categories.
Ensure no symbols ($, commas, etc.) are in numeric fields.
Contact support with:
A screenshot of the error message
The row/data causing the issue
A copy of the CSV file
✅ Summary: Most CSV import errors in Church Metrics come down to small mismatches in formatting or names. By starting with the sample template, keeping headers intact, and checking categories/campuses carefully, you can successfully import your past data without issues.