Compare
KI BMS: the alternative to concludis
What moving from concludis to KI BMS actually looks like in 2026.
KI BMS is what people use when concludis stops fitting. Below is the honest side-by-side - same product surface, different posture: hosted in Germany, no third-party trackers, one honest price - plus the migration mechanics that decide whether the switch lands in an evening or in a quarter.
At a glance
concludis is right for German mid-markets and larger employers who value multi-posting to many job boards, a mature careers page, and an established German vendor with a support tradition. Multi-posting is a genuine strength we don't have at that breadth. KI BMS is right for modern teams up to ~100 people who want KI pre-sort as a default, value public prices and monthly cancellation, and don't want a procurement marathon with quote-only pricing. Both are German-centric; they target different buyer generations.
Switching
What moving from concludis actually looks like
The switch goes in three rough phases: export from concludis, import into KI BMS, and reorganise what came over. Most people allocate an evening for it. The export side is where the time goes - concludis hands you a CSV/JSON dump and the field mapping isn't always obvious; once that's resolved the import is a couple of minutes. We don't paywall the import path or pretend it's a pro-only feature, and you can run both side-by-side while you decide.
KI BMS vs concludis: feature comparison
When to pick which
Pick KI BMS when
Pick concludis when
Where concludis is strong
concludis has been established in the DACH market for a long time and has a genuine strength many younger tools don't have at that depth: multi-posting. Distributing one role to many job boards, career portals and agency channels at once and collecting responses centrally is a domain where concludis brings experience and integration breadth. If your recruiting bets on reach across many channels, that's a concrete advantage.
On top is the established-vendor reality: German legal grounding, support tradition, an onboarding that's guided rather than left to you. For organisations that prefer introducing a tool with a contact person over a free tier, that's an important factor.
What the other generation of tooling does differently
KI BMS was built a generation later and did three things differently. KI is a default, not a gradually rolled-out feature - every role has KI screening with readable reasoning available, no surcharge and no activation project. Setup is self-serve rather than an onboarding phase - free tier, onboarding in one morning. Prices are public instead of quote-only - €0, €1, €10 per month, monthly cancellation, self-serve refund within 30 days.
What we deliberately don't build at that breadth: multi-posting to dozens of channels. Our default is your own careers page plus a public application form that writes straight into the pipeline. If your reach runs across many external job boards, concludis is objectively stronger there - no argument.
Concrete selection grid
Two questions decide. One - is multi-posting to many external job boards central to your recruiting? Yes -> concludis has the matching breadth. No -> continue. Two - do you want KI as a default, public prices and a setup in hours? Yes -> KI BMS. No, you want guided onboarding and an established vendor -> concludis.
Export from concludis
Find the export option in concludis's account settings. Most tools provide a CSV or JSON download. Save the dump locally - that's the source of truth for the next step.
Map fields in KI BMS
Open the import tool in KI BMS. concludis's field names rarely match KI BMS' 1:1; the import flags any unmapped columns so you can pair them up before anything commits.
Run the import
Run the import. KI BMS shows a preview of the first parsed rows in the import dialog so you can sanity-check the column mapping + a sample of records before anything commits. If you're nervous about a large dump, import a small subset first, verify it landed the way you expected, then run the full file.
Re-create your views, tags, saved searches
concludis-specific UI metadata (custom views, saved filters, in-app annotations) doesn't transfer with the data export. Spend an evening rebuilding the views you used most - usually a 30-minute job once you've done it once.
Cancel concludis when you're confident
Run both side-by-side for a couple of weeks if you want to be sure. When you're confident, cancel the concludis subscription from their side. KI BMS keeps your export option self-serve in account settings - no lock-in either direction.
Switching from concludis
The five questions we get most often before someone moves their data over.
Start with KI BMS
Free plan, no credit card. We host in Germany. Export + delete are self-serve.
Read next
Full KI BMS vs concludis
Established German e-recruiting with multi-posting vs modern KI-default tool. Procurement vs self-serve.
Read
KI BMS vs Prescreen: Austrian ATS in the onlyfy group vs lean specialist
Established DACH ATS in the XING / onlyfy group vs lean KI-default tool with public pricing.
Read
KI BMS vs Onlyfy by XING: network-driven vs KI-driven
Onlyfy has the XING network as a source. KI BMS has KI as a tool. Comparison for DACH recruiting teams.
Read
KI BMS vs HeavenHR: lean HR suite or dedicated ATS?
Lean HR suite vs dedicated ATS - decision grid for 10-50-person German SMEs.
Read