Custom CRM templates

Use a custom schema when your CRM is not one of the eight built-in providers, when you need a record type the built-in schema does not cover, or when you want to produce a CSV for a tool other than a CRM (an enrichment service, a data warehouse, a downstream script).

A custom schema is a list of fields you define. Each field has a key (the output column name), a label, a type, and optional flags for required and validation.

Seven types are supported: Text, Email, Phone, Number, Date, URL, and Yes/No. Email and phone get automatic cleanup and validation (lowercased and trimmed; non-digits stripped except a leading +). Text, Number, Date, URL, and Yes/No are stored exactly as you enter them and pass through to your CRM unchanged. If you need date parsing or URL validation, do it before upload.

Operelio flags invalid emails, phones, and missing required fields with the exact row and reason. Other types pass through without validation. A Required flag generates a warning per row when that column is empty or unmapped, but does not block export. Review warnings before pushing to your CRM.

On the Format step, click Build a custom schema. Add each field in turn: label, type, required flag. Reorder fields with the up and down arrows, remove fields with the trash icon. Save the schema so it appears in your Load schema menu next time.

Custom schemas are stored on your account, so you can reuse them across different source files. Pro supports 5 custom schemas; Team supports 25; Agency supports 75.

When you reach the cap (5 schemas on Pro, 25 on Team, 75 on Agency), the New schema button shows an upgrade prompt. Delete a schema first to free a slot.

Schemas can be edited or deleted from the Schema library. Editing a schema doesn't change historical jobs that used the old version: those keep their original field set.