Churnor
Import SaaS customer data with CSV
Use a CSV to add customer records and an optional last-active timestamp to a Churnor product environment. This guide explains the supported fields, identity mapping, and what the import can and cannot bring in.
Before you import
Sign in to Churnor and create or select a product environment. Prepare a CSV with a header row and one row per customer. The import runs inside the authenticated dashboard; the public guide does not expose customer records.
Choose a stable external customer or user ID that you can also send with product events. Churnor uses that identifier to associate later activity with the imported record.
Map the columns you have
In the dashboard, upload a CSV and map one column to the required Customer / User ID field. The import also supports optional columns for email, name, subscription plan, monthly recurring revenue (MRR), and last active time.
- Customer / User ID: required; use a consistent external identifier.
- Email and name: optional customer details.
- Plan and MRR: optional billing context. MRR is interpreted as a monthly amount.
- Last active: optional parseable date or timestamp. Churnor records it as imported activity context.
Column names can differ from Churnor’s field names because you map them in the import screen. Review the sample rows and mappings before starting the import.
What happens to imported data
Churnor creates or updates customer records using the selected external ID. When a last-active value is mapped, the import records an imported_login event at that timestamp. The import result reports created and updated customers, imported activity records, failed rows, and any row errors.
A customer list and last-active timestamp are not a full historical product event stream. For detailed historical activity, send events through the Events API with their original timestamps. CSV import does not import prior billing transactions.
Keep IDs consistent across sources
Use the same external customer ID in CSV and product event requests. Billing providers may use their own customer IDs, so check the matching rules before connecting a provider.
Read the customer ID matching guide · Learn how to send product events