What this importer does
Use the Data Importer to send spreadsheet data into Lumonic.
You map columns in Excel → fields in Lumonic
You can save the setup so next time is one click
You can test first (Dry run) so you don’t accidentally write bad data
Before you start (2 minutes)
Install the Lumonic Excel add-in from the Add-in Store.
Sign in: Lumonic tab → Sidebar → enter email → code → Log in
Prep your sheet:
One header row (no blank headers)
Data is consistent below each header
Avoid merged cells in the data you’re importing
Two core concepts
Template = saved recipe
A Template saves your whole setup so you can reuse it later:
schemas
field mappings
options (like Dry run / skip errors)
import history
Use a template when: you’ll run this import again (most people will).
Schema = one table of data
A Schema is one “block”/table of data you’re importing.
Use multiple schemas when:
your data is in separate ranges (not one clean rectangle)
you’re importing different types of tables (summary vs detail)
you want different cadences (run one daily, another weekly)
Example:
A1:B10= Loan balancesD1:D10= Loan value
(ignore column C)
✅ That’s two schemas
Quick start (recommended for your first import)
Open Excel → Lumonic tab → Sidebar
Go to Data Importer
Click Create and name your template (example: “Q3 Revenue Import”)
Add one schema
Select a clear range (a simple table with headers)
Run a Validation (dry run)
Fix any issues
Run Import (real write)
Step-by-step
1) Create (or pick) a Template
Open Data Importer in the sidebar
Choose an existing template OR click Create
Name it clearly (you’ll thank yourself later)
Good names: “Holdings Upload”, “Q4 Pipeline Update”, etc
2) Build a Schema (what to import)
Click Add Schema
Note: you can add multiple schemas if you are importing from multiple tabs or ranges
Fill out “Dimensions” (this is the whole import)
Think of each row (or each cell in your values range) as answering:
Who is this for? What are we updating? For what date? Under what scenario?
In the sidebar, you’ll fill those answers using either:
a picklist value (one fixed choice for the whole import), or
an Excel range (read it from cells, row-by-row)
Picklist vs Excel range (rule of thumb)
Use a picklist when the value is the same for everything you’re importing.
Use an Excel range when the value changes across rows/columns.
Examples:
You’re importing one company’s data → picklist for Entity
You’re importing many companies in one table → range for Entity
All rows are for the same Effective Date → picklist or a single cell
Each row has its own Effective Date → range
In the UI:
Use the search (magnifying glass) to pick from Lumonic
Use the sheet/range button to select cells in Excel
One small but high-impact tip: dynamic ranges
If you add rows over time, use the * option (shown in the UI) so your ranges auto-expand. That way your template doesn’t break every month.
Field-by-field: what it means + how to fill it
Namespace (required)
Plain English: what kind of thing you’re updating in Lumonic (Company, Security, etc.).
Pick Company if your Entity column contains companies
Pick Security if it contains securities
This choice controls what appears in the Entity list
Entity (Entity ID / Entity Name/External ID) (required)
Plain English: who each value belongs to.
You have two ways to identify entities:
NAME (e.g., “Company Name”) — easiest for humans.
Note that this must exactly match or nearly fuzzy match to the names as listed in Lumonic.
ID (Lumonic ID) — most reliable if names can vary
External ID — If you have setup one of your own system identifiers in Lumonic, you can use that here too
Choose picklist vs range
Picklist: you’re importing for one entity
Range: your sheet has an Entity column (many entities)
Tip: If you’re seeing the dropdown list (like Facebook, etc.), you’re using the picklist. If you’re seeing Sheet1!J23:J27, you’re using a range.
Field ID (required)
Plain English: what you’re updating (the Lumonic field/metric).
Again, you can fill it two ways:
Picklist: you’re writing one field (e.g., “Revenue”) for many entities
Range: your sheet has a Field column (each row might be a different field)
Use NAME unless you already store Lumonic field IDs. Names are usually enough and easier to debug.
Effective Date (required)
Plain English: the date the value is “for”.
If every row is the same date: point to one cell or choose a date
If each row has its own date: select the date column range
Common mistake: typing dates as text. If Excel doesn’t recognize it as a date, validation will flag it.
Values (required)
Plain English: the actual numbers/text you want written to Lumonic.
Often the importer can infer this once Entity/Field/Date are set
If it guesses wrong, override it and select the exact value range
Always sanity-check the highlighted values range before importing.
Additional Dimensions (usually optional, often fixed)
These apply “labels” to your data. Most teams set them once per import.
Scenario Name (common)
Plain English: Actuals vs Budget vs Forecast, etc.
If everything is Actuals: set Predefined Value = Actuals
If Scenario changes in your sheet (by row or by column): use a range
Important: Don’t turn on fuzzy matching here unless you’re okay with “Budget v1” and “Budget” potentially being treated as the same thing.
Period Type
Plain English: monthly vs yearly vs quarterly cadence.
If you always import monthly: keep your default (often M)
Change only if you know the target data is yearly/quarterly/etc.
4) Common patterns
Pattern A: “Many entities, one field”
Entity = range (entity column)
Field ID = picklist
Effective Date = picklist or single cell
Values = value column
Pattern B: “Many entities, many fields” (your example layout)
Entity = range
Field ID = range
Effective Date = range
Values = the values block
Pattern C: “One value, lots of defaults”
Entity = picklist
Field ID = range
Effective Date = range
Values = range
Pattern D: “All Ranges”
