VECTORIO
EN
EnglishDeutsch

“Day one after the deal: two forests, two address books, and everyone needs to reach everyone”

One address book after the merger.

Contacts, users and groups of both companies appear in each other's address list.

The problem
  • Colleagues from the acquired company are missing in Outlook for weeks.
  • Group memberships break when users move between forests.
  • Nobody can say who changed which address, and when.
With PROTOR
  • Contacts, users and groups of both companies appear in each other's address list.
  • Group memberships follow their members into the target forest.
  • Every run is previewed, capped and recorded in a signed audit trail.

From today to the first result.

What you do today

CSV imports and scripts

Colleagues from the acquired company are missing in Outlook for weeks, and group memberships break when users move between forests.

With Connectype

Live LDAP to AD: 10,000 objects created in 27.6 s. A change run of 20 changes takes 2.7 s, and every run is previewed first.

Your first step

Run the preview against a copy of both directories – nothing is written until you agree.

one afternoon
How it runs

Directory contacts, synced as deltas. Step by step.

10,000 contacts are read with change tracking, checked, mapped to Active Directory attributes and written — rejected rows land in a dead-letter file for review.

PROTOR · Directory contacts, synced as deltasrunning
Contacts fileCSV SubscriberSchema ConformanceSchema ConformMap to AD schemaAD Schema MapperGAL attributesExpression MapperQuality GateSync.QualityGateDirectory exportCSV PublisherRejected contactsCSV Publisher
  1. Contacts fileCSV Subscriber
  2. Schema ConformanceSchema Conform
  3. Map to AD schemaAD Schema Mapper
  4. GAL attributesExpression Mapper
  5. Quality GateSync.QualityGate
  6. Directory export · Rejected contactsCSV Publisher · CSV Publisher
nodes
csv-source-contacts → CSV.Subscriber
schema-conform → ETL.SchemaConform
ad-schema-mapper → AD.SchemaMapper
expression-mapper → ExpressionMapper
quality-gate → Sync.QualityGate
csv-target-contacts → CSV.Publisher
csv-dlq-contacts → CSV.Publisher
10,000 contacts with change trackingmapped to Active Directory attributesdead-letter file for rejects
  1. Contacts fileReads rows from a CSV file in batches.
  2. Schema ConformanceEnforces required fields and safe types.
  3. Map to AD schemaMaps source fields to directory attributes.
  4. GAL attributesMaps and transforms fields with expressions.
  5. Quality GateChecks rows against rules and routes failures to a dead-letter table.
  6. Directory exportWrites rows to a CSV file.

A real workflow from our end-to-end test suite; the designer view is illustrated.

What you get. From the first pilot.

Contacts, users and groups of both companies appear in each other's address list.

Group memberships follow their members into the target forest.

Every run is previewed, capped and recorded in a signed audit trail.

Why your tools fall short.

×

Cloud sync services need a connector into the tenant that many security teams have to approve first.

×

Hand-written scripts overwrite values that admins added on the target.

×

Migration tools are built for a one-off move, while both directories run side by side for years.

What drives it
  • Acquisitions and carve-outs with long integration periods
  • Audit requirements for every identity change
  • Exchange hybrid address formats (x500, legacyExchangeDN)

Your pilot. Three steps.

1

Your data shape

Tell us what data you have, where it lives and what the result must be.

2

A scoped pilot

On your data and your hardware, with the success measure written down first.

3

A clear decision

You see the result against that measure — and keep every workflow and record.

Beta · design partners wanted

Bring us your hardest data problem. Let's solve it together.

A short pilot on your data and your hardware. We agree on what success looks like before we start.