The Template library

The Template library is the place to browse every ready-made column mapping Operelio ships. Each template is a pre-built recipe that takes a known export (a LinkedIn Sales Navigator CSV, an Apollo People export, a Mailchimp subscriber list, and so on) and maps its columns to a specific CRM's import fields. Cleanup defaults are baked in too: trim whitespace, standardize email, split a single Name column into first and last, normalize country values.

There are two ways to reach the library. The public catalog lives at /templates and is open to anyone, including visitors who have not signed up yet. Inside the app, signed-in users get the same browser at /app/tools/crm_formatter/templates, with a Saved mappings link in the page header that opens your own mappings on a dedicated page.

Browsing the library is the right starting point when you want to see what is possible before uploading a file, or when you know the source and destination but want to confirm a template covers it.

Every template card shows three things at a glance. The source platform on the left (LinkedIn, Apollo, Mailchimp, and so on), the target CRM on the right (HubSpot, Salesforce, Pipedrive, Zoho, Monday, Freshsales, Close, or Copper), and a one-line description of what the template does. Below the description, a small footer shows how many fields the template maps. To narrow the catalog to a single category, use the pill row at the top of the grid.

Click any card to open the detail page. The detail page shows the exact source columns the template expects, the CRM field each one maps to, the cleanup settings that run by default, and a sample of what the output looks like. Reading the detail page before you upload is the fastest way to confirm a template fits your data.

Three filters narrow the library quickly. The category pill row at the top groups templates by source type (LinkedIn, Data Providers, Email Marketing, Google & Microsoft, Ecommerce, Events & Scheduling, Forms, Support & Messaging, CRM Migration). The search box matches against template names and descriptions, so typing "hubspot" or "apollo" jumps to the relevant slice. And the source-and-CRM logos on the hero strip act as a visual reference for what is covered.

The fastest path is usually: pick the category that matches your export, then scan the remaining cards for your target CRM. If you already know both the source and destination (for example Apollo to Salesforce), search for the source name and the matching template will be in the first few results.

Picking a template from the public catalog sends you to sign-up with the template carried in the URL. After signing in, the CRM Formatter opens with the template pre-applied. Upload your file on the next step and the columns map across automatically. Review the mapping, adjust anything Operelio got wrong, and run.

Picking one from the webapp library is a single click on the Use template button on each card. Either way, you can still override every individual column mapping on the Map step, and you can tweak cleanup settings (case standardization, email normalization, phone formatting) on the Review step before running.

Templates are a shortcut, not a constraint. If you apply a template and then change three column mappings, those changes apply to this job only. The template itself is not modified. To make your changes permanent, save the result as your own mapping (Pro, Team, and Agency plans).

There are two types of templates in the system. Built-in templates are the 167 Operelio ships, available on every plan; they show in the Template library on both surfaces. Saved mappings are ones you created yourself by mapping a file manually and clicking Save mapping; they live on /app/mappings, reachable from the Saved mappings link in the Template library header.

Inside the CRM Formatter, after you upload a file, the Quick Import row shows built-in templates ranked by how many of your columns match. To load one of your own saved mappings instead, use the Load mapping dropdown on the Map step. Both paths reach the same Map step, so you can switch approaches mid-job without losing work.

On the public catalog at /templates, only built-in templates show; saved mappings live behind login because they belong to your account.

If your export does not match any of the 167 built-ins, you have two options. The first is to pick the closest one and adjust the mapping; templates fill in sensible defaults, and the auto-mapper handles any remaining unmatched columns against the target CRM format. The second is to skip templates entirely and map your file manually against any CRM format or the Generic format. Manual mapping is fast on well-named columns: Operelio auto-detects "First Name", "first_name", "fname", and similar variations.

If the same source comes up repeatedly and you would rather not redo the work, save your mapping after the first run. From then on, your saved mapping lives on /app/mappings and is one click away from the Load mapping dropdown on the Map step, ready to apply to every subsequent file.

For a deeper look at how Operelio suggests templates automatically once you upload a file, see the Quick Import templates guide.