How long does switching from Greenhouse actually take?

An evening for most accounts. The export from Greenhouse is the slow step - the import side runs in minutes once the field mapping is settled. Larger teams (50+ seats with custom field schemas) sometimes split it across two sessions: import first, reorganise the next day.

Will I lose data when I switch?

Nothing structural. The CSV/JSON export from Greenhouse preserves the data: records, fields, history, and attachments come over intact. What doesn't transfer is anything tied to Greenhouse-specific UI metadata (custom views, saved searches, in-app annotations) - those don't sit in the export, they sit in the source product's UI. Plan an evening to rebuild your most-used views once you're in.

What about my existing Greenhouse subscription?

Run both side-by-side until you're confident, then cancel Greenhouse from their side. We don't lock you in - export from KI BMS is one click in account settings, same as import.

Is the import path free?

The import button is open on every plan, including the free tier - we don't paywall the way out of a competitor. The data going in still has to fit your plan's per-type quotas (the free-tier caps are listed on /sales); paid plans raise those caps. If you're moving a large set, check the caps first or write to /support and we can advise.

Can I get help with the switch?

Yes. Write to /support - both founders see those threads directly. Reply within a working day. For the field-mapping itself we typically resolve things in one or two exchanges; if your dataset is unusually large or Greenhouse's export shape is unfamiliar, we'll say so up front.

KI BMS

Pricing

Compare

KI BMS: the alternative to Greenhouse

What moving from Greenhouse to KI BMS actually looks like in 2026.

Switching

ATS

Comparison

Tech recruiting

Julia YukovichCo-Founder + CEO

·March 20, 2026·

2 min read

KI BMS is what people use when Greenhouse 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

Greenhouse is clearly the leader for US tech companies that have a dedicated recruiting team with their own sourcers, coordinators, and a documented hiring process. For a 1-3 person German HR team that doesn't think in English, the tool is often too big, too expensive, and too complex to configure. KI BMS isn't trying to clone Greenhouse for Germany - it's a deliberately leaner tool that serves the 80% recruiting reality where nobody needs 18 approval stages.

Switching

What moving from Greenhouse actually looks like

The switch goes in three rough phases: export from Greenhouse, import into KI BMS, and reorganise what came over. Most people allocate an evening for it. The export side is where the time goes - Greenhouse 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 Greenhouse: feature comparison

	Ours KI BMS	Theirs Greenhouse
Pipeline depth (approvals, stage gates)	Mid	Very high
Sourcing tools	Talent pool
Structured interviews + scorecards
KI fit-score built in		Third-party plugin
Branded careers page
DACH languages + GDPR		GDPR yes, UI EN-centric
Setup time	Hours	Weeks with implementation partner
Price	€0 / €1 / €10 per month	5-figure per year (quote-only)
Minimum term	None	1+ year
Hosting region	Germany	US primary, EU region available

When to pick which

Pick KI BMS when

You're 1-30 staff and recruiting is part of one HR person's job, not the whole job.

The workflow is reasonable: New -> Review -> Screening -> Interview -> Offer. Not 18 stages with approvals.

GDPR is required, German wording subtleties (Du form, salutation) shouldn't feel translated.

You want KI pre-sorting as a default, not as a paid third-party plugin.

Pick Greenhouse when

You have a recruiting team with dedicated coordinators, sourcers, and a documented process per role.

100+ roles a year, multi-country, multi-currency - Greenhouse's depth is then justified.

English is your working language and procurement accepts 5-figure annual contracts.

What Greenhouse does well - and expensively

Greenhouse's strength is depth. Structured interview plans where multiple interviewers each complete their own scorecards. Approvals at stage transitions. Complex permission models where a hiring manager can't see every note. Sourcing extensions that pull LinkedIn profiles into the tool. These features are real and indispensable in a 100-person recruiting team.

But they come at a cost: a 5-figure annual contract, a 4-12 week implementation project with a partner, and a UI tuned for US workflows. In a German mid-market setup with 2-3 HR people, most of the depth is unused complexity.

What KI BMS deliberately leaves out

KI BMS has no approval stages. If a hiring manager needs to sign off, it happens before creation or verbally; the ATS only records recruiting itself. We don't have a LinkedIn sourcing extension - the talent pool as a manual list is enough for the volumes we serve. We don't have multi-country logic with currencies and tax IDs.

What we deliberately do well: KI pre-sorting with real per-application reasoning, real-drag pipeline with WS sync, email templates with auto-send on stage change, a careers page that's public in seconds. The tool is 100% built for the German-speaking mid-market - and we say clearly where it doesn't reach.

Step by step

Export from Greenhouse

Find the export option in Greenhouse'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.

Account settings → Export / Download data

Pick the broadest format the tool offers (usually JSON)

Map fields in KI BMS

Open the import tool in KI BMS. Greenhouse's field names rarely match KI BMS' 1:1; the import flags any unmapped columns so you can pair them up before anything commits.

Account settings → Import

Resolve the mapping prompts the tool surfaces

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

Greenhouse-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 Greenhouse 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 Greenhouse subscription from their side. KI BMS keeps your export option self-serve in account settings - no lock-in either direction.

Switching from Greenhouse

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.

Written by

Julia Yukovich

Co-Founder + CEO

Julia is one of the Co-Founders. She handles design, product direction, and most of the support replies that arrive in the morning.

julia.yukovich at aicuflow dot comLinkedIn