Bulk import lets you create several sponsors at once from an Excel file instead of adding them one by one. It pays off when you already have your partners in a spreadsheet — typically ten or more. The wizard has five steps and runs validation on the data before anything is written. It imports text fields and the category assignment; logos cannot be uploaded through the import and have to be added by hand afterward.
Decide which Sponsors instance you are importing into. The Sponsors content feature can be added to an event more than once (for example Conference partners and Media partners), and the Import tab is separate for each of them — sponsors land in the instance you are currently in.
Prepare your data in Excel. You can either download the template from the admin or use your own file — you map the columns by hand in the second step, so the column names do not matter.
Review your category names. A category is required for every sponsor. If a category with that name does not exist yet, the import creates it — exactly as written in the file, so a typo creates one extra category.
Prepare the logos separately. The import cannot handle them; you add them by hand in each sponsor's edit panel after the import.
Decide what happens when someone clicks the logo (external website, sponsor profile, or nothing). The value goes into the file as a word, and it has to match what you filled in the other columns.
In the admin, go to Content and open the Sponsors instance you want to import into (the instance name sits in the switcher next to the Content heading). The section header has four tabs: Sponsors, Categories, Settings, and Import. Open the Import tab.
The first step of the wizard gives you two paths:
Download template and fill it in. The template is an XLSX file with a single sheet named Sponsors, a header row, and one sample row of dummy data (Example Sponsor s.r.o.) — delete that row before you import, see the pitfall below. The file name includes the name of the event you downloaded it from.
Upload your own Excel with your own column names. You set the mapping to sponsor fields by hand in the second step.
Template headers come in the language of the admin interface — a Czech admin gives you Název, Kategorie, Webové stránky; an English one Name, Category, Website. That has no effect on the content: both variants have the same columns in the same order and the same sample row, and the mapping step works regardless of the header language.
The description column, on the other hand, follows the event's content language — on an event with English content it is named Description - EN.
Either way, you then click Upload & parse and the wizard moves on to mapping.
Name (required) — The sponsor name. Also the key used to detect duplicates.
Category (required) — If the category does not exist in the event, the import creates it — see below.
Website (optional) — The URL must start with https://.
Logo click action (website/profile/none) (optional) — The value is written as a word: website, profile, or none.
Description - EN (optional) — Tied to the event's content language.
E-mail (optional)
Phone (optional)
LinkedIn, Twitter / X, Instagram, Facebook, YouTube (optional) — Links to the sponsor's social networks.
Only Name and Category are required — you can spot them by the asterisk on the destination field in the mapping step. Columns you leave unmapped are skipped.
The list of destination fields ends at YouTube. The logo, the status (Published / Hidden), and the sponsor's order within a category are not among them, so the import does not set them.
Unlike the speaker import, where display level and status are entered as numeric codes, sponsors take text. The allowed values are spelled out in the column name itself:
website — clicking the logo opens the sponsor's external website. Fill in the Website column too, with an https:// URL.
profile — clicking opens the sponsor's profile inside the platform. Fill in the description too, and optionally contacts and social networks.
none — clicking the logo does nothing; the logo is purely visual. Nothing else to fill in.
At the top of the screen there is a step indicator: Upload → Mapping → Relations → Preview → Results. You can move back between steps.
1. Upload. Download the template (optional) or upload your Excel directly through the file picker. Click Upload & parse.
2. Mapping. The wizard reads your file's headers and shows them in an Excel column — Sample values — Map to field table, along with the number of rows found. For each column, pick the destination field from the dropdown. Unmapped columns are skipped. The mapping is not saved anywhere — you set it up from scratch on every import. Click Validate & preview — the wizard takes you straight to the preview.
4. Preview. The wizard shows a summary: Total / Valid / Warnings / Errors / Duplicates. Below the summary is a per-row table with each row's status — a valid row is marked green, a duplicate row carries a duplicate icon and a message that a sponsor with this name already exists. Row numbers match the row numbers in Excel, so the first data row is 2 (row 1 is the header). Nothing has been written yet — this is your last chance to go back and fix the file. If the summary looks good, click Import.
5. Results. After the import finishes, the screen shows the final counts: Created / Skipped / Errors. From here you can go to the sponsor list (Continue to list) or download a detailed CSV report on every row (Download report (CSV)) — useful when you need to trace which row did not import and why.
A category is required for every sponsor, and the import can create one — if a category with the name from your file does not exist in the event, it is created during the import. The sponsors are assigned to it and you will see them in the sponsor list.
A newly created category, however, does not appear on the home screen of the microsite or the attendee app on its own. If you want it there, turn on the Display on the home screen of the microsite and attendee app toggle for that category on the Categories tab after the import. While you are there, check its Display level as well (values 1, 2, 4) — it drives the order of categories and the number of logos per row.
For sponsors, a duplicate is determined by the name alone. A row is a duplicate if:
a sponsor with the same name already exists in the event, or
the same name appears more than once in the file.
Duplicate rows are not imported — the wizard skips them and, from repeated rows, imports the first occurrence. The Preview step shows the duplicate count up front; in the Results, skipped rows are counted under Skipped.
This means the import does not overwrite existing sponsors. To change sponsors that are already in the event, use the bulk actions on the Sponsors tab (change category, change status, delete).
Upload logos. Neither the template nor the mapping has a column for a logo or a logo URL. Add logos by hand in each sponsor's edit panel after the import.
Set the status. There is no status field (Published / Hidden) among the destination fields, so the import does not determine it — check the status in the sponsor list afterward.
Set the order within a category. Sponsor order inside a category is set by dragging rows in the list, not by a column in Excel.
Update existing sponsors. Duplicate rows are skipped; handle bulk changes with the bulk actions in the sponsor list.
The downloaded template has the first data row pre-filled with dummy data, including the category Main sponsors, the website example.com, and a phone number with a country code. In Preview it shows up as a valid row. Delete it before you fill in your own data — otherwise you end up with an invented sponsor in the list and an extra Main sponsors category alongside it.
Because the import creates missing categories, a name that does not match is not an error that Preview would catch. Gold sponsors and Gold Sponsers are two different categories to the import, and both exist after it runs. Before you upload the file, compare the values in the Category column with what you have on the Categories tab — ideally by copying the names from there rather than typing them from memory.
A category created during the import has its sponsors assigned correctly, but display on the home screen of the microsite and the attendee app has to be turned on by hand on the Categories tab. If the sponsors are not visible on the home screen after the import, this is the first place to check — along with the status of both the sponsor and the category (sponsors are visible only when both are Published).
Rows are compared against sponsors that already exist in that instance, so a second import of the same file ends with everything flagged as a duplicate and skipped (in Preview you see Valid 0 and Duplicates equal to the number of rows). Always check the duplicate count before you click Import — a higher number than you expect means some of those sponsors are already in the event. The import will not create them again, and it will not overwrite them.
For sponsors, a duplicate is detected by name only, not by website or e-mail (speakers, by contrast, are matched on first and last name together). If you have two branches or two divisions of the same company entered under an identical name, only the first goes through. Disambiguate them in the name (for example by country or division), or one of them drops out.
Bulk import handles text fields and the category assignment only. With 20 partners that means 20 edit panels in which you add the logo after the import (SVG, PNG, JPEG, or GIF; 16:9 ratio; max. 500 KB). Plan time for it, and prepare the logos in a consistent format up front.
The wizard does not remember your column mapping — you enter it from scratch after every upload. If you import repeatedly (partners trickle in over time), keep the same column names and order in your file as in the downloaded template. Mapping then takes a few seconds and you will not miss a field.
