Initializing workspace...

Switching

Six weeks, and we

will name the hard parts.

Most migration pages promise a weekend. Ours takes six weeks for a fund with real history, because reconciling a capital account against a spreadsheet somebody has been maintaining since 2021 is not something software does alone. Here is the actual sequence.

What comes across, and how

Import by import.

Contacts & companies
CSV from any CRM, or a direct pull from Affinity and 4Degrees. A large file processes overnight rather than timing out.
Automatic
Deal pipeline & stages
Stage mapping is proposed, then confirmed by you before anything writes.
Automatic, confirmed
Email & calendar history
OAuth through DSignal Connect. The relationship graph backfills from your own history.
Automatic
Cap table positions
Carta export, or a spreadsheet in almost any shape — the import wizard maps your columns and you confirm the mapping before anything writes.
Automatic, confirmed
Capital accounts & history
Every call and distribution since inception, reconciled line by line against your records.
Needs a person
Historic LP reporting
Past PDFs are attached, not parsed. We do not retro-fit numbers we cannot trace.
Needs a person
The sequence

Nobody stops working.

You keep your current tools running the whole way. The switch happens at week six, not week one.

Week 1

Read-only mirror

We connect to your existing systems read-only and mirror the data in. Nothing in your current stack changes, nobody's day changes, and you get to look at your own fund inside the product before committing to anything.

We do this
Week 2–3

Reconcile the money

Every capital call and distribution since inception, matched against your records line by line. This is the part that takes two weeks and this is the part where a human has to look at it. Any figure that does not tie out gets flagged rather than smoothed over.

Together
Week 4

Your team, in parallel

The whole team gets logins and works in both systems for a week. Unlimited seats is why this is possible — there is no per-seat cost to running a parallel period, which is the usual reason migrations get rushed.

Your team
Week 5

LPs and founders

DSignal Portfolio invitations go out, founders get their reporting logins. We stage this after your team is comfortable, because the first external-facing thing should not be the first time anyone has used the product.

Together
Week 6

Cut over, and cancel

Old systems go read-only for 90 days, then you export and close them. We will tell you which of them you should actually keep — if you have Carta and you need 409As, the answer is Carta.

You decide
Who the “we” is above

The people doing this build the product.

Every week in that sequence marked “We do this” or “Together” is our professional-services team, and they sit with the engineers who ship the software rather than at a partner firm. That matters at exactly one moment: week three, when the reconciliation turns up something your old system did that no setting in ours covers — a fee structure, a side letter, a waterfall term. At most platforms that becomes a workaround you maintain forever. Here it goes to the roadmap with a stated date, and the fix ships to every fund, including yours.

None of it is mandatory. A fund with clean history and no legacy vehicle can do the whole thing self-serve and never speak to us; services are scoped and quoted per engagement, only when you want the hands on the wheel.

And on the way out

The exit is not a hostage negotiation.

Every collection exports to CSV. The API is open on every paid plan, from Solo up. There is no export fee and no notice period on data access. A platform that keeps customers through export friction is not being chosen, it is being tolerated — and a fund that cannot leave has no leverage at renewal, which is a bad thing to sell people.

Scope your own migration.

Tell us what you are on now. We will come back with the week-by-week and the parts that need a person.