Skip to main content

Data Mapping - hausmanager to SINGU FM

This article documents how each data area from hausmanager was transferred to SINGU FM, including what was migrated, how it was mapped, and where limitations apply.

A
Written by Anna Machay

Complete Term Reference

hausmanager

SINGU FM

Notes

Ticket

Ticket

Logic retained; status names differ

Aufgabe (from scheduled Maßnahme)

Inspection

Only tasks from Maßnahmen with a schedule

Aufgabe (ad-hoc or from ticket)

Ticket

Tasks without a schedule → Ticket

Maßnahme (template, with schedule)

Inspection Definition

Without a schedule: NOT migrated

Checkliste

Checklist / Tasks

Answer type converted to LogicCorrectness

Stammdaten-Baum

Ticket Categories

Tree structure retained; top node = "My House"

Servicebereich / Leistungsbereich

Ticket Classification

Used on Inspections and Buildings

Kategoriematrix (Kategorie 1 & 2)

Ticket Categories

Matrix transformed to tree structure

Objekt-Gruppe

Site Group

1:1

Liegenschaft / Objekt

Site

1:1

Gebäude

Building

1:1

Einheit / Raum / Etage

Location

All 3 types → Location (hierarchy via parentId)

Bauteil / Anlage

Equipment

QR code from hausmanager retained

Zählerbauteil (meter component)

Equipment (Meter)

Technical data retained

Zähler (reading)

Meter Reading

1:1

Adresse – Eigentümer

Customer

Adresse – Nutzer / Bewohner

Customer

Adresse – Firma / Dienstleister

Partner

Virtual person created for each partner

Adresse – Mitarbeiter

User

Only if linked to a user account in hausmanager

Nutzer

User

With role mapping (see Users section)

Abschluss / Teilabschluss

Visit (on Ticket / Inspection)

Arbeitsauftrag / Leistungsnachweis

Ticket History

Not a separate object — archived

Dokument (external / internal)

Ticket History

Files retained

Kostenfelder (Soll / Ist)

Ticket History

As text summary, not structured data

Protokoll / Log

❌ Not migrated

Excluded by agreement

Wartungsvertrag (service contract)

Equipment → Attributes

No dedicated module in SINGU FM

Nutzungsart – Gebäude

Building Type

Nutzungsart – Einheit / Raum

Location Type

Dokumentgruppen

Document Categories (Glossary)

Files without a group received a default value

Zählertyp m³

Meter medium: Water

Automatic mapping

Zählertyp kWh

Meter medium: Electricity

Automatic mapping

All other meter types

Meter medium: Electricity

Default assignment


Master Data

Ticket Categories (formerly Stammdaten-Baum)
The master data tree was migrated as Ticket Categories, preserving the hierarchical structure and original labels. The top-level node is "My House." Template-level information stored within master data was not migrated — SINGU FM does not have equivalent template functionality.


Checklists
Checklists including all items were fully migrated as Checklists / Tasks. Because SINGU FM does not support multiple freely-definable answer options, all answer types were converted to LogicCorrectness (Yes / No / N/A). Conditional behaviors linked to checklist answers (e.g., automatic ticket creation triggered by a specific answer) are not supported and were not migrated.

Classifications Service area classifications (Leistungsbereiche) were migrated as Ticket Classifications and are used on both Inspections and Buildings. The two-level category matrix (Kategorie 1 and 2) was transformed from a matrix to a tree structure and stored as Ticket Categories.


Users & Roles

Role Mapping

hausmanager Role

SINGU FM Role

Description

Administrator (1)

Admin

Full access

Leitung / Management (2)

Board

Management view — read only

Objektbetreuer (3)

Coordinator

Object coordinator

Hausmeister (4)

Technician

Technical executor

Externer (5)

Customer

Tenant or client

Dienstleister (6)

Partner

External service provider

Address Records
Owners and residents (Eigentümer, Nutzer/Bewohner) were migrated as Customers. Company addresses were migrated as Partners.

Because SINGU FM can only assign ticket responsibility to a person (not a company), a virtual person was created for each Partner address, linked to a user account, to enable responsibility assignment.

Employee address records were migrated as Users only if linked to an active user account in hausmanager — address-only records without a user account were not transferred.


Object Access
Object access permissions (Objektfreigabe) were transferred to the Responsible Matrix at Site level. If a user cannot see an object, check:

Admin → Master Data → Tickets → Responsibility Matrix.


Object Structure

Hierarchy Mapping

hausmanager

SINGU FM

Objekt-Gruppe

Site Group

Liegenschaft / Objekt

Site

Gebäude

Building

Einheit

Location (via parentId)

Raum

Location (via parentId)

Etage

Location (via parentId)

⚠️ Key difference: In hausmanager, floors (Etagen) and rooms (Räume) were separate levels. In SINGU FM, all three (Einheit, Raum, Etage) are the same object type — Location — linked hierarchically via parentId. You will not see separate tabs for floors and rooms; look for them as Locations under the Building.

Files on Objects
Files stored at unit, room, or floor level in hausmanager have been consolidated to Building level in SINGU FM. Navigate to the Building record and open the Files tab.

Responsible Matrix
Responsible Matrix assignments (Objektadresszuordnung) were migrated from hausmanager address records to SINGU FM users and projected to the top-level Site. This defines who is automatically assigned responsibility for tickets at a given site.


Equipment & Installations

Equipment (formerly Bauteile) Every Bauteil/Anlage became Equipment in SINGU FM. Retained: QR codes (those assigned to equipment only), custom fields (as Attributes), files and documents, and meter components (as Equipment with type Meter).


Inspection Definitions (formerly Maßnahmen) Only Maßnahmen with a defined recurrence schedule were migrated as Inspection Definitions. Maßnahmen without a schedule (used as task templates / Aufgabenvorlagen) were not migrated — there is no equivalent in SINGU FM.


Tasks, Tickets & History

Task Origin Mapping

hausmanager

SINGU FM

Aufgabe from a scheduled Maßnahme

Inspection

Aufgabe from a Ticket

Ticket (with task information)

Ad-hoc Aufgabe

Ticket

Ticket (without linked tasks)

Ticket

Ticket (with linked tasks)

Task record is leading — handled as part of task migration

Ticket History
The following were archived in Ticket History and are not separate objects in SINGU FM: work orders (Arbeitsaufträge), service reports (Leistungsnachweise), external and internal documents, planned and actual costs (Soll/Ist-Kosten, stored as text summary).

Checklists on Tasks
Checklists were migrated only where attached to migrated Inspection Definitions. Checklists on ad-hoc tasks or ticket-sourced tasks could not be migrated due to a structural limitation in SINGU FM.

Completions and Visits
Completions and partial completions (Erledigungen / Teilerledigungen) were migrated as Visits on Tickets and Inspections.


Meters

Meters (Zähler) were migrated as Meters; readings (Zählerstände) as Meter Readings. Medium assigned automatically:

hausmanager unit

SINGU FM medium

Water

kWh

Electricity

All other units

Electricity (default)

Documents related to meters are stored on the associated Equipment record, not on the Meter itself.


Documents & Files

Document type in hausmanager

Where to find in SINGU FM

Files on Bauteil / Anlage

Equipment → Files tab

Files on Einheit / Raum / Etage

Building → Files tab

Files on Ticket

Ticket → History

Arbeitsaufträge / Leistungsnachweise

Ticket → History

Service contracts (Verträge)

Equipment → Attributes ⚠️

Building plans and documentation

Building → Documentation

Document groups (Dokumentgruppen) were migrated to document categories in SINGU FM. Files with no group assigned received a default value.

Did this answer your question?