Halo's built-in spreadsheet importer lets you load clients, users, assets, tickets, SLAs, and 20+ other record types in bulk — no scripting, no API calls. Fill in the template, upload, done.
What You Can Import
From client records to SLA priorities and recurring invoices — Halo covers every major data type you need to populate before go-live, or migrate from your old platform.
Core Platform
Organisations and their site locations. Supports create and update via a configurable matching field. Custom fields and site-specific fields (prefixed "SF") are supported.
End users and contacts linked to clients and sites. Match on email or username to update existing users. Custom fields are supported.
Staff members who work tickets in Halo — name, email, team, role, and job title. Used to pre-populate your agent directory before go-live.
Historical or migrated tickets. Linked to existing clients and users — import those first. Include the ticket ID column to match to existing records.
Ticket category hierarchy. Use ">" as a separator for nested levels — e.g. Hardware>Laptop>Battery. The Type ID links to the correct ticket type.
SLA definitions including name, work hours calendar, response tracking, fix-by targets, and optional auto-release settings.
Priority levels tied to SLAs — response and resolution targets in hours or days, colour codes, and auto-extend end-of-day settings.
Notes, updates, and time entries against existing tickets. The ticket must already exist in Halo — reference it by its Request ID. Custom fields are supported.
Physical address records linked to users or sites. Includes primary/inactive flags, active date ranges, and lat/long coordinates.
Assets
Hardware and software assets linked to clients and users. Includes warranty dates, supplier SLA, and support for asset fields (prefixed "AF") and custom fields.
Categories for classifying assets — e.g. Laptop, Server, Mobile, Software. Controls which fields appear on assets and how they are grouped in reports.
Knowledge & Content
Articles with summary, full details, resolution text, author, and date. Assign to multiple FAQ lists by comma-separating values in a single cell.
Saved response templates for agents — stored with a name, group, and HTML body. Agents insert them into ticket actions to speed up replies.
Assign users to Halo distribution lists by list name plus user ID or email address — for group notifications and shared ticket visibility.
Projects & Scheduling
Tasks within Halo projects, linked to milestones, clients, users, budgets, and agents. Project milestones must exist before task rows can reference them.
Calendar entries with subject, attendees, type, start/end dates, and optional ticket linkage. Supports all-day and timed appointments with agent reminders.
Service catalogue entries linking a service name and category to ticket types or templates. Controls what users see when raising a request through the portal.
CRM opportunity records with contact details, company name, pipeline status, and agent assignment. Used to seed a new Halo CRM instance with existing pipeline.
Rows in custom-built data tables. Can be linked to any Halo entity using a key column. Supports custom field columns and a configurable matching key for updates.
Suppliers & Stock
Vendor records including contact name, phone numbers, email domain, website, address, and accounts ID. Supports create and update via a configurable matching field.
Contracts with suppliers — reference number, description, start/end dates, linked SLA, and up to three named key contacts.
Products and billable items with sales price, cost price, group, asset type linkage, supplier, and supplier part code. Supports create and update.
Stock quantities by item, location, and bin. A separate tab handles serialised asset imports — linking individual serial numbers to stock records.
Billing & Finance
Billing agreements with clients — hours, billing period, charge rate, invoice description, contract reference, and next invoice date.
Scheduled invoices across two sheets: headers (client, dates, repeat period) and line items (item, quantity, price, tax). Lines reference the header by position number.
Line items on existing quotations — item name, quantity, unit price, tax name, nominal code, and comment. The quotation must already exist in Halo.
How It Works
No API setup. No scripting. Download the template, fill it in, and upload it via Configuration in Halo.
Download the example spreadsheet for the data type you need from the templates section below.
Add records to the IMPORT DATA sheet. Don't alter blue column headings. Format dates as yyyy-MM-dd.
Each data type has its own import location inside Configuration. See the navigation reference below.
Halo shows a preview of every row before importing. Select or deselect individual rows, then click Start.
The Result column updates per row — successful rows are live immediately. Fix any failures and re-upload those rows.
Import Rules
These rules apply to every import type. Get them right first time and your import will be clean.
Columns highlighted in blue in the template map directly to Halo's field names. Leave them exactly as they are — even capitalisation matters. If you don't have data for a blue column, leave the rows blank rather than removing it.
Using yyyy-MM-dd (e.g. 2026-01-15) is unambiguous and works regardless of how your Halo instance date format is configured.
To import custom field values, add a column named after the custom field as it appears in Halo's custom field list — typically prefixed with cf, e.g. cfamountdue. The custom field must already exist in Halo before importing.
For types that support updates — Assets, Users, Clients & Sites, Suppliers, Items, and others — set a unique identifier in the import setup screen. If Halo finds a matching record it updates it; if not, it creates a new one.
Quick Reference
1 for true, leave blank for falseFinding Field Names
If you need to import to a field that isn't on the template, you can reveal every field name in Halo by appending ?showfieldnames=true to any Halo URL. This shows the API field name alongside each label — copy it exactly as your column header.
For failed rows, open your browser's developer console (Fn + F12) to see the exact error from the API.
Example Templates
Each spreadsheet includes an IMPORT DATA sheet (fill this in) and an INSTRUCTIONS sheet (read this first). All 26 templates in one zip.
26 spreadsheets covering every Halo data type. Each includes column definitions, instructions, and example data.
Download Templates (.zip)26 files · Updated with Halo releases
FAQ
cf, e.g. cfamountdue. The custom field must already exist in your Halo configuration before you run the import. This works for Tickets, Assets, Users, Clients & Sites, Opportunities, Customer Contracts, Items, Services, and Custom Tables.Every Allied ESM Halo implementation includes full data migration. We review your files, handle the import sequencing, and validate everything before go-live.