Data import via GraphQL

Master data is the information related to Owner, Property, Unit and Tenant. To request these information it is required to have authorization tokens.

To understand how authentication works in EverReal, read Authentication page.

For importing master data to EverReal it is required to keep the following order as shown in the chart:

This chart shows the recommended data import flow

1. First, the owners should be created/imported by using the following endpoint: Owners Mutation.

2. Once the import is finalised for the owners the next endpoint which should be used is Property groups.

Property groups is recommended to be created but it's not necessary or a precondition for creating properties. If you want to bulk inherit descriptions (for e.g. amenities, location) to several properties it's recommended to create them.

3. In the next step the properties should be created by using the following endpoint: Property Mutation. The following checklist provides informations about creating properties. The checklist summarizes the overall areas which might cause issues.

• Address information is split in street, street number, zip code and city

• Avoid having additional information in address information (e.g. in street number "Hinterhaus")

• No duplicate properties --> Multiple properties with the same address information are not possible

• Properties are not property groups. Properties should be broken down to the building entrance (Hauseingang) for explicit assignment

4. Going further in the following step Units Mutation, units can be created and within creation assigned to associated property. What needs to be taken care of is as followed:

• For UnitInput {name:} we would recommend to insert the value for unit location for e.g. 1. OG links

• For UnitInput {mainStorage:} the value can be set to TRUE or FALSE if the information is not availabe

• For UnitInput {floorNo:} we need data format integer, in most of the ERP-systems the location of the unit is available for e.g. EG, 2. OG mitte etc. Therefore floorNo could be extracted from this information. Why we are doing this? As can be seen in the Screenshot, we create a stacking plan

Stacking Plan in EverReal

1. The last step is Tenants Mutation, where tenants can be created and within creation assigned to associated units. As a result of the tenants import, the unit status is being automatically updated from EverReal.

   1. Contract start date is in the past and there is no contract end date: unit status is leased

   2. Contract start date is in the future: unit status is vacant, re-leased

   3. Contract start date is either in the past or in the future but there is a contract end date in future: unit status is terminated