FAQ
The ten questions we are asked before every rollout
Implementation time, imports, integrations, onboarding, permissions and security. Answered properly rather than deferred to a call.
Implementation
How long does implementation actually take?
Most teams have a working register within a week. Day one is the import: you upload a spreadsheet or an export from your previous tool, map the columns, and review the preview before anything is written. That step usually takes under an hour, even for several thousand rows.
The rest of week one is labeling physical equipment and connecting your directory and device management tools. From week two you switch on reminder rules and scheduled reports. Larger rollouts across many sites take longer to walk the floor, but the software side is finished in the same first week.
Data import
Our inventory is a messy spreadsheet. Can you still import it?
Yes, and messy is the normal starting point. The mapping step lets you point each of your columns at an Eze IT field, skip the ones you no longer need, and set a default for rows where a value is missing. You see a full preview of what will be created before you commit.
Duplicates are detected on serial number, asset tag and MAC address, and rows that fail validation are listed with the reason so you can correct them in place rather than reworking the file. If the result is not what you expected, one action rolls the entire import back for thirty days.
Can we migrate history from our old asset tool?
Yes. Alongside current assets you can import assignment history, repair records and disposal certificates, and Eze IT will attach them to the correct asset by serial number or asset tag.
Where your old tool exports history in a format we do not recognize, send us a sample during your trial and we will map it for you before you commit to anything.
Integrations
Which systems does Eze IT connect to?
Twenty four integrations ship natively, covering directory and identity, device management, service desk, finance and procurement, HR, and alerting. That includes Microsoft Entra ID, Okta, Google Workspace, Intune, Jamf Pro, Kandji, Jira Service Management, ServiceNow, NetSuite, Workday, Slack and Microsoft Teams.
Anything not on the list can be handled through the REST API or outbound webhooks, which post asset events to a URL you control. Integrations are available from the Growth plan upward.
Do we need to install an agent on every device?
No. Eze IT has no agent and does not need one. Hardware and installed software details come from the device management platform you already run, such as Intune, Jamf Pro or Kandji.
If you do not use an MDM, assets can be created by import, by scanning a label with a phone, or manually. Nothing is installed on a user machine at any point.
Onboarding
What does onboarding include, and is training provided?
Every plan includes guided import, field mapping help and directory connection at no extra cost. There is no setup fee and no migration charge.
Scale customers get a named contact and a written rollout plan covering label printing, site by site scanning and the reminder rules to switch on first. Live training sessions for administrators and technicians are included, and recordings are added to your workspace so new starters can watch them later.
Permissions
How do permissions and roles work?
A permission is a role plus a scope. The role decides what someone can do, from read only through technician and manager to full administration. The scope decides where, whether that is one site, a region, a department or the entire organization.
So a technician in Denver can manage Denver equipment without seeing cost centers elsewhere, and a finance colleague can pull global reports without being able to edit an asset. Custom roles let you hide individual fields, such as purchase price, from people who do not need them.
Can we give an auditor or contractor limited access?
Yes. Read only auditor access can be granted with an expiry date, so it closes automatically when the engagement ends rather than waiting for someone to remember.
Read only viewers are free and unlimited on every plan, and every action they take is recorded in the same audit trail as everyone else. Nobody needs a shared login.
Security
Where is our data stored and who can see it?
Data is encrypted in transit with TLS 1.3 and at rest with AES 256, and each customer workspace is logically isolated so one account can never query another. You choose your hosting region during setup, in the United States, the European Union or the United Kingdom, and your records stay in it.
Access by our own staff requires a specific approved reason, is limited in time, and is written to an access log you can request at any point. We do not sell customer data, and we do not use it to train models.
What happens to our data if we stop using Eze IT?
You can export everything at any time, including asset records, full change history and attachments, in CSV and JSON. That is available on every plan and does not require a support request.
If you close your account, the workspace stays available in read only mode for thirty days so you can retrieve anything you missed. After that it is permanently deleted, including backups, within a further thirty days, and we confirm the deletion in writing.
Still deciding?
The pricing page lists every plan limit in full, and the security page covers data protection, access controls, audit trails and backups in detail. If your question is specific to your estate, ask us directly.
Ask in person
Bring the awkward questions to the demo
Migration edge cases, permission models, residency requirements and the reports your auditors insist on. Thirty minutes with someone who has answered them before.