BOS

Implementation

From your current system to live in BOS.

A migration that stops and tells you, rather than one that finishes quietly with gaps in it.

How the import works

BOS includes a migration capability for bringing CRM records across from an existing system, run as a reviewed job rather than a one-shot upload.

Why that matters: a record that arrives without an owner is invisible to anyone whose visibility is scoped to their own or their team's records, so an import that half-succeeds looks exactly like missing data months later. We walk the import with you rather than handing you a file uploader.

The principle

An import that half-succeeds looks exactly like missing data months later.

Sequence

The stages

Scoping

What moves, what does not, and what it should look like on the other side.

Workspace

Your tenant, your roles, your pipeline stages.

Dry run

The import is reviewed against your data before records are written.

Import

Executed only after the dry run is clean and you have approved the result.

Configure

Teams, territories, quotas, approvals and the process itself.

Talk through what would move.