Migrate from Atera to HubSpot Service Hub

Atera Tickets map directly to HubSpot Service Hub Tickets. Subject, status, priority, customer association, technician/assignee, created/modified timestamps, and notes migrate 1:1. The technician field is resolved via the Owner mapping (see Agent/Technician mapping). Tickets with no assigned technician are remapped to a nominated fallback HubSpot user during pre-flight validation. Ticket tags migrate as comma-separated values in a custom Ticket field.

Atera Customer records map to HubSpot Companies. Company name, domain, billing address, and custom fields migrate as Company properties. The Atera customer-to-device association is preserved by linking Atera asset data to the Company via a custom Asset association object in HubSpot. Duplicate company names are flagged during pre-flight for the customer's admin to resolve or merge before import.

Atera Contact records map to HubSpot Contacts. Name, email, phone, role, and custom fields migrate as Contact properties. The Contact-to-Customer (Company) association is resolved by matching the Atera customer_id foreign key against the HubSpot Company ID generated during the Company import phase. Contact tags migrate to HubSpot Contact properties or as a comma-separated custom field.

Atera technicians map to HubSpot users by email address. We extract all distinct technician emails referenced on Tickets, Customers, and Contracts and match them against the HubSpot destination User table. Any technician without a HubSpot user account is held in a reconciliation queue. Atera's per-technician license gating requires coordination: when the CSV row count exceeds available HubSpot seats, we sequence the import in batches that respect the seat limit and coordinate with the customer's admin on any Atera-side disable/enable cycles. Active vs inactive status in Atera maps to HubSpot user active/inactive.

Atera Contracts (hourly, fixed-term, retainer, project-based with custom rates) have no direct HubSpot standard object equivalent. We create a HubSpot Custom Object named Contract with properties for contract type, rate, billing period, SLA tier, and customer association (lookup to Company). The contract rate structure is preserved as a custom property. Flat-rate retainer entries are mapped against the custom Contract object with a retainer type flag.

Atera SLA policies define response time and resolution time thresholds tied to priority level. We map SLA name and thresholds to a HubSpot Custom Object (SLA Policy) linked to Tickets via a custom lookup field. Alternatively, if HubSpot Business Hours are configured, SLA timers are linked to Business Hours with priority-to-first-response and priority-to-resolution custom properties on the Ticket. The customer chooses the SLA model during scoping.

Atera allows custom fields on Tickets, Customers, Contacts, Contracts, SLA Policies, and Agents. We detect the full custom field schema during discovery, generate HubSpot custom properties of equivalent type (text, number, date, dropdown, checkbox), and map values during import. Custom field dependencies on Atera forms are documented in the schema output for the customer's admin to reconfigure in HubSpot.

Atera KB articles (title, body text, category, attachment links) migrate to HubSpot Knowledge Base articles. HTML body content may require sanitisation if Atera uses non-standard HTML tags unsupported by HubSpot's knowledge base renderer. Categories migrate as HubSpot Knowledge Base categories. Embedded images and attachment links are preserved as URLs pointing to the Atera export; the customer's admin replaces them with HubSpot-hosted assets post-migration. The pre-built HubSpot Knowledge Base importer is used as the ingestion path for KB content.

Atera tags on Tickets and Customers are simple string values. Tags on Tickets migrate as a custom Ticket property (comma-separated or HubSpot's tag feature if enabled). Tags on Customers migrate as a custom Company property. No value transformation is required.

Atera RMM device records (workstations, servers, network hardware) carry hardware specs, software inventory, and health status. We create a HubSpot Custom Object named Device with properties for hostname, type, OS version, health status, and customer association (lookup to Company). The device-to-customer linkage is preserved via the Company lookup. If the customer does not require device-level tracking in HubSpot, we flag this as out-of-scope and document the Atera asset export for use with a dedicated RMM tool.

Billable time logged against Atera tickets feeds the PSA billing layer. We map billable hours, rate, and total to a HubSpot Custom Object named Time Entry, linked to the Ticket and Contact. Retainer entries and flat-rate billing require a separate mapping against the Contract custom object. The customer chooses whether billing data migration is in scope; if excluded, we document the Atera billing export for reimport into a dedicated billing tool.

Integration credentials and OAuth tokens are platform-bound and cannot be transferred. We document all integration endpoints, connected services, and configuration settings during discovery so the customer's admin can reconfigure them post-migration in HubSpot's integrations marketplace.