Settings: Import

The import settings can be found in your website’s backend (wp-admin) under WP-ImmoMakler → Settings → Import.

Settings Overview

Label	Type	Default	Description
Automatically Delete OpenImmo Files	Select	after 180 days	Number of days after which already imported OpenImmo files are automatically deleted.
Smart Full Sync	Checkbox	active	When active, a full sync only removes deleted properties, updates existing ones, and adds new ones. When disabled, the entire inventory is deleted first and then rebuilt from scratch.
Full Sync: Only Update Changed Properties	Checkbox	active	When active, only properties whose data has actually changed are reimported during a full sync. Significantly speeds up large full syncs.
Use Publication Date from OpenImmo	Checkbox	active	When active, the stand_vom field is used as the initial publication date. When disabled, the date of publication on the website is used.
Mark Sold/Rented Properties as Reference Properties	Checkbox	inactive	When active, properties marked as sold or rented during import are automatically converted to reference properties.
Ignore Delete Commands from CRM Software for Reference Properties	Checkbox	—	When active, reference properties are not deleted even if the CRM software sends a delete command.
“regionaler_zusatz” as District	Checkbox	inactive	The OpenImmo field regionaler_zusatz is classified as a subcategory of the actual city (e.g., for districts or boroughs).
Split Location at the ”/” Delimiter into City and District	Checkbox	inactive	The OpenImmo field ort is split at the ”/” delimiter, and the part after it is classified as a district under the actual city — e.g., “Munich / Allach” becomes the city “Munich” with the district “Allach”.
Split Location at the ”-” Delimiter into City and District	Checkbox	inactive	The ort field is split at the ”-” delimiter (e.g., “Munich-Allach”), including all typographic variants of the hyphen (e.g., en dash ”–”, em dash ”—”). Leave this disabled if your locations have a hyphen in their name (e.g., “Villingen-Schwenningen”). Can be enabled independently of splitting at the ”/” delimiter.
Group Locations by Federal State	Checkbox	inactive	The OpenImmo field bundesland is added as a parent category, so that locations are sorted under their respective federal state.
Sort Locations Outside the Home Country Under Their Respective Country	Checkbox	inactive	Locations of properties outside the configured home country are sorted under their respective country. For these locations, “Group Locations by Federal State” does not apply.
Automatically Determine Vienna Districts from Postal Code	Checkbox	inactive	For Austrian properties (iso_land = AUT), the Vienna city district is determined from the postal code and added as a separate location nested under the city “Wien” — without modifying the regionaler_zusatz field.
Always Use Geo-coordinates from CRM Software	Checkbox	inactive	When active, geo-coordinates from OpenImmo are used even when the property address is set to “do not publish”.
Image Quality During Import	Number (10–100)	82	Compression quality for the JPG/PNG image sizes generated during import. The WebP and AVIF conversions each have their own separate quality setting. Lower values produce smaller files and speed up the import; the default value of 82 matches the WordPress default. Only affects future imports.
Convert Property Photos to PLUS	Select	WebP	Target format for the automatic conversion of JPG/PNG property images during import. WebP is typically 25–35% smaller than JPG and retains more detail sharpness (requires WordPress 5.8+); AVIF produces files up to 70% smaller with slightly less detail sharpness (requires WordPress 6.5+); No conversion keeps JPG/PNG. A format your server can’t write (ImageMagick or GD) isn’t offered in the selection — the setting states the reason. Only affects future imports. Replaces the former “Convert Images to AVIF” checkbox: websites where it was active are automatically set to AVIF; all others start converting to WebP from the next import onward.
WebP Conversion Image Quality PLUS	Number (10–100)	82	Compression quality specifically for the WebP conversion (only takes effect when “WebP” is selected above). The WebP quality scale roughly matches JPEG’s, which is why the WordPress default value of 82 is used here — even so, WebP files come out noticeably smaller than JPG at the same value. Only affects future imports.
AVIF Conversion Image Quality PLUS	Number (10–100)	60	Compression quality specifically for the AVIF conversion (only takes effect when “AVIF” is selected above). The AVIF quality scale does not correspond to JPEG’s: AVIF already achieves very good rendering at noticeably lower values. The default value of 60 delivers high image quality at roughly half the file size compared to the value 82; higher values significantly increase file size without a visible quality gain. Only affects future imports.
Exclude Property Photos from Optimization Plugins PLUS	Checkbox	active	Automatically excludes property photos from EWWW Image Optimizer, Imagify, Smush, and Converter for Media, as long as a conversion is selected above — a second conversion brings no benefit, degrades image quality, and burns credits with paid services. ShortPixel and manual bulk optimizations can’t be controlled via code; add /wp-content/uploads/immomakler/ there yourself as an exception.
Clear Website Cache After Import	Checkbox	active	When active, the cache of common caching plugins is cleared after every change to the property inventory.
Import Notifications: Email on Successful Import	Checkbox	—	When active, an email is sent upon successful import. Error messages are always sent.
Import Notifications: Recipient Name	Text	—	Name of the recipient for import notifications.
Import Notifications: Recipient Email Address	Text	—	Email address for import notifications (errors and uploads).
Author of Imported Properties	Select	current user	WordPress user to whom imported properties, contact persons, photos, and attachments are assigned.

Caution

If you temporarily disable Full Sync: Only Update Changed Properties — for example, to regenerate all images or apply a PHP filter to all imports — remember to re-enable the option afterwards.

Location Hierarchy During Import

Six settings control how WP-ImmoMakler builds a multi-level hierarchy in the location taxonomy (immomakler_object_location) during import. They can be used individually or combined:

• “regionaler_zusatz” as District classifies the regionaler_zusatz field as a subcategory below the actual city (e.g., a district below the city).
• Split Location at the ”/” Delimiter into City and District splits the ort field at the ”/” delimiter and classifies the part after it as a district under the actual city. If the CRM software delivers, e.g., “Munich / Allach” (or “Munich/Allach”), this produces the city “Munich” with the nested district “Allach”. The district term keeps its plain name but gets an SEO-friendly URL slug prefixed with the city (e.g. munich-allach). This keeps same-named districts of different cities as separate terms — “Zentrum” in Munich (munich-zentrum) is a distinct district from “Zentrum” in Leipzig (leipzig-zentrum).
• Split Location at the ”-” Delimiter into City and District uses ”-” as a delimiter, so “Munich-Allach” or “Munich - Allach” is split. All typographic variants of the hyphen are also treated as delimiters, e.g. the en dash ”–” and the em dash ”—”. Leave this option disabled if your locations have a hyphen in their name (e.g., “Villingen-Schwenningen”), as these locations would otherwise be split as well. Both splitting options can be enabled and combined independently of each other — so, for example, bilingual location names like “Bozen/Bolzano” keep their slash untouched, while “Bozen - Gries” is split into city and district.
• Group Locations by Federal State adds the bundesland field as a parent category, so that locations are sorted under their federal state.
• Sort Locations Outside the Home Country Under Their Respective Country sorts locations of properties outside the configured home country under their respective country. For these locations, grouping by federal state does not apply — they are placed directly under their country.
• Automatically Determine Vienna Districts from Postal Code determines the Vienna city district from the postal code for Austrian properties and nests it as a separate location below “Wien”, without modifying the regionaler_zusatz field.

Combined, this produces a three-level hierarchy:

Federal state → City → District or borough

Pro Tip

You can also build custom location hierarchies in code. The immomakler_after_generate_and_set_terms action fires during import once all taxonomy terms of a property have been set. Using the passed ImmoMakler instance and its make_term_child() method, you can create additional parent/child relationships.

make_term_child() expects the terms in this order:

1. Child term — the term that is nested underneath
2. Parent term — the term it is placed under
3. Taxonomy — e.g. immomakler_object_location
4. Language code — e.g. de

The following example reverses the “regionaler_zusatz” as District setting: instead of nesting regionaler_zusatz below the city, regionaler_zusatz becomes the parent term that the city is nested under. For example, if the CRM software delivers the city “Blaubeuren” with regionaler_zusatz = “Schwäbische Alb”, this produces the hierarchy Schwäbische Alb → Blaubeuren.

add_action(
  'immomakler_after_generate_and_set_terms',
  function ( int $post_id, array $openimmo_data, \ImmoMakler $immomakler ): void {
    if ( ! empty( $openimmo_data['regionaler_zusatz'] ) && ! empty( $openimmo_data['ort'] ) ) {
      $immomakler->make_term_child(
        $openimmo_data['ort'],               // 1. Child term (city), e.g. "Blaubeuren" ...
        $openimmo_data['regionaler_zusatz'], // 2. Parent term (regionaler_zusatz), e.g. "Schwäbische Alb"
        'immomakler_object_location',        // 3. Taxonomy
        $openimmo_data['language_code_short'] ?? 'de' // 4. Language code
      );
    }
  },
  10,
  3
);

You might also be interested in

• Taxonomies (Categories)
• Automatic Import via Cron Job
• Styling the Search Form in the Customizer
• Creating Menu Items