How long does switching from d.vinci actually take?

An evening for most accounts. The export from d.vinci 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 d.vinci preserves the data: records, fields, history, and attachments come over intact. What doesn't transfer is anything tied to d.vinci-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 d.vinci subscription?

Run both side-by-side until you're confident, then cancel d.vinci 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 d.vinci's export shape is unfamiliar, we'll say so up front.

KI BMS

Pricing

Compare

KI BMS: the alternative to d.vinci

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

Switching

ATS

Comparison

DACH

Julia YukovichCo-Founder + CEO

·March 26, 2026·

2 min read

KI BMS is what people use when d.vinci 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

d.vinci is right for German corporates and large mid-markets from 250 staff that want an established ATS with deep approval workflows, multi-level permissions, and long market presence. KI BMS is right for modern mid-markets up to 100 staff that want KI pre-sort as a default, value monthly contracts, and don't want a 6-month implementation process. Both are German-centric, both understand GDPR - they target different generations of buyers.

Switching

What moving from d.vinci actually looks like

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

	Ours KI BMS	Theirs d.vinci
Approval workflows + permissions	Mid	Very deep
KI fit-score built in		First KI features from 2025
Careers page builder
Multi-posting job boards
Audit log + GDPR auto-anonymisation		Manually configurable
Hosted in Germany
Multi-voice scorecards
Setup time	Hours	Weeks with implementation partner
Pricing model	Public (€0 / €1 / €10 per month)	Quote-only, individually negotiated
Minimum term	None - monthly	1-3 years typical
API + webhooks + MCP		API yes, MCP no

When to pick which

Pick KI BMS when

You're up to 100 staff and recruiting has no dedicated 6-month implementation slot.

You want KI pre-sort with reasoning as default - not as a KI module rolled out from 2025.

Public prices and monthly cancellation matter to you - no 3-year contract with quote-only pricing.

Pick d.vinci when

You're 250+ staff and need multi-level approval workflows with fine-grained permissions.

Established market presence with implementation-partner network has concrete procurement value.

Your corporate compliance expects a tool 20+ years in market - not a 2026 player.

d.vinci has built a German recruiting tool since 2002, growing through many corporate compliance audits. The result: a tool with German legal grounding, German implementation partners, German implementation tradition. If you're buying an ATS in a 1,000-person company, d.vinci is a vendor that speaks procurement's language.

Strength is depth: multi-level approval workflows where hiring manager - works council - leadership all sign off, fine-grained permissions where a coordinator only sees roles in one division. That's corporate reality, and d.vinci does it maturely.

What the other generation of tooling does differently

KI BMS was built 22 years after d.vinci. We did three things differently: KI is default, not module (every role has KI screening available, no surcharge). Setup is self-serve, not implementation (free tier, 8-minute onboarding, no partner). Prices are public, not quote-only (€0, €1, €10/month, monthly cancellation). These three decisions don't fit corporate procurement reality - they fit modern mid-market reality where HR values speed and clarity.

Concrete selection grid

Three questions lead to the right pick. One - do you have a works council co-signing ATS decisions? Yes -> d.vinci has the matching approval stack. No -> KI BMS suffices. Two - do you need permissions per division, site or subsidiary? Yes -> d.vinci. No -> KI BMS. Three - how many roles per year? <30 -> KI BMS clearly; 30-100 -> both possible, KI BMS cheaper; 100+ -> d.vinci stack-fit is better.

Step by step

Export from d.vinci

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

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

Switching from d.vinci

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