Triumph Foundation — FlintKit Onboarding Plan (Rev 2)

Prepared for: Triumph Foundation (Andrew Skinner, Christine Haroutunian) Engagement: Kindful → FlintKit (formerly Vessel) migration, configuration, and Year 1 platform onboarding Revised: June 3, 2026

What changed in this revision

Joshua's relationship-reset call with Andrew is complete. Andrew knows a team and a plan are coming, and that Kim Jetton will reach out to schedule.
New constraint — Andrew is out ~June 29 to July 5 (last week of June through the July 4 weekend). He is unavailable for any client-facing step in that window and returns ~July 6/7.
New risk — Kindful may try to remove Triumph before July 20. This is Andrew's central worry. The plan now treats one action as the thing that neutralizes it entirely: an immediate, verified export. Once that export is confirmed, an early Kindful shutoff stops being a data-loss event of any kind.
Kim Jetton becomes Andrew's day-to-day contact and owns scheduling and coordination from here.

The team

Director — Joshua Smith: Primary client relationship, commercial questions, expectation setting.
Project Manager — Kim Jetton: Andrew's day-to-day contact. Timeline, coordination, kickoff logistics, status updates, dependency tracking, scheduling.
Product Owner / Lead Developer — Denver Stewart: Migration execution, FlintKit configuration, scope build, validation. Becomes product owner of FlintKit.
Support — Brendan Yost: Migration knowledge, technical escalation, advisory. OOO June 17 to 26.

Key dates and constraints

Kindful shutoff: July 20 — the stated hard deadline. Treated as potentially earlier given Kindful's posture (see risk below).
Kindful early-removal risk. Andrew reports Kindful is pushing to get Triumph off the platform before July 20. Mitigation: secure a verified full export immediately (Phase 0). Once secured, early cutoff is no longer a data risk.
Andrew OOO ~June 29 to July 5. No client-facing decisions, approvals, or training in this window. All client inputs are gathered before June 27.
Brendan OOO June 17 to 26. Work needing Brendan is front-loaded before the 17th or scheduled after the 27th.
July 3 is the observed Independence Day holiday (July 4 falls on a Saturday). Plan around a light/closed July 3.
DeepRoots go-live June 13 frees Brendan for the knowledge handoff the week of June 15.
Migration script already exists and has been run once against Triumph's Kindful data. The core technical risk is already retired. What remains is reassessment, configuration to parity, a clean re-run, and validation.

Data safety note (the headline)

The single most protective action — and the direct answer to Andrew's fear — is preserving a current, complete, verified Kindful export now, this week, while access is still guaranteed. If Kindful removes Andrew's login, it may also remove our ability to export, so this happens first.

Once that export is confirmed and stored safely, it no longer matters whether Kindful pulls the plug on July 20, July 10, or July 1. Triumph's data is safe with us, and every step downstream runs on our schedule. This is what makes the assurance Joshua gave Andrew true. It is non-negotiable and it happens in Phase 0.

Phase 0 — Reset, kickoff, and data safety

Timing: Week of June 3 (now), parallel to DeepRoots.

✅ Joshua's reset call with Andrew is complete. Andrew knows the team and plan are coming.
Kim sends the team intro email and engagement map to Andrew, Christine, and the Triumph team, introducing the four roles and establishing herself as the day-to-day contact.
Kim schedules the remote kickoff for the week of June 15 — both Andrew and Brendan are available then, ahead of either OOO window.
Denver secures a fresh, complete, verified Kindful export immediately, and confirms/locks Kindful access credentials now in case Kindful removes Andrew's access. Top priority. This is the answer to the early-shutoff worry.
Denver gets access to the existing migration script and prior migration output.

What we tell the client: Your data is being secured this week and will be safe no matter what Kindful does or when. Here is your team, here is your day-to-day contact, and here is the plan — built around your time out.

Phase 1 — Reassessment and knowledge handoff

Timing: June 15 to 16. Owners: Brendan → Denver.

Brendan walks Denver through the existing migration script and prior output.
Together they reassess the remaining source systems (Kindful, plus Eventbrite, SignUp Genius, Square): what's migrated, what remains, what's changed since the first run.
Output: a migration scope and configuration spec Denver executes against while Brendan is out.
Added — collect everything from Andrew before he leaves. At kickoff (week of June 15), Kim gathers every client input Denver will need for the OOO window: parity expectations, configuration decisions, scope sign-off, and access. Nothing should be waiting on Andrew during his late-June/July-4 absence.

Phase 2 — Configure to parity and build scope

Timing: June 17 to 26, during Brendan's OOO. Owners: Denver leads, Kim coordinates.

Denver configures FlintKit to mirror Triumph's Kindful setup: custom fields, segments, donor and gift structures, core reports.
Build the five contracted scope items: Spanish-language site, Square embed, ClickSend, stacked logo and favicon, and the volunteer data piece.
Kim tracks progress against the spec, holds non-urgent questions for Brendan's return, and parks genuine blockers for June 29 rather than interrupting his time off.

Phase 3 — Full migration

Timing: June 29 to July 2. Owners: Denver leads, Brendan support.

Denver re-runs the migration against current Kindful data plus the additional sources from Phase 1.
Validate fidelity against the parity checklist from the Phase 1 spec.
Brendan available for spot-checks and escalation, not driving.
Note: This window falls during Andrew's OOO — by design. Migration execution has no client dependency, so the heads-down work is deliberately placed here. The window is Mon–Thu, avoiding the July 3 observed holiday.

Phase 4 — Parallel run, training, and cutover

Timing: July 7 to 16, timed for Andrew's return. Owners: Kim coordinates, Denver executes, Joshua with client.

Parallel run: Triumph verifies their data and workflows in FlintKit against Kindful (if Kindful is still live — see contingency).
Kim coordinates training for Andrew and Christine the week of July 7.
Go / no-go decision (~July 10), then cutover by ~July 15–16 so Triumph operates in FlintKit.
Several days of margin before the July 20 shutoff.

Phase 5 — Begin improving

Timing: After July 20, off the critical path. Owners: Kim, Denver, with Brendan available.

Year 2 enhancements, website redesign and brand refresh, and the AI and automation features that flow to active FlintKit clients.
Sequenced after go-live so nothing here pressures the July 20 deadline.

Contingency — if Kindful pulls the plug before cutover

Because the verified export is secured in Phase 0, an early Kindful removal is a data-safety non-event. Specifically:

If Kindful goes dark before the parallel run: we skip the side-by-side comparison and validate against the secured export instead, then stand up FlintKit as the live system. The parallel run is a comfort check, not a dependency.
If it happens during Andrew's OOO: Denver and Kim proceed on the secured data. Nothing requires Andrew until training and cutover, when he's back.
Bottom line: the only way an early shutoff becomes a real problem is if we don't have the export. So the export happens this week, full stop.

Critical path at a glance

Secure the verified Kindful export and lock access — this week (Phase 0). Neutralizes the early-shutoff risk.
Collect all of Andrew's inputs and approvals before June 27 (gathered at the June 15 kickoff).
Brendan → Denver handoff and spec, June 15–16 (Phase 1).
Denver configures and builds during the OOO window, June 17–26 (Phase 2).
Clean migration and validation, June 29–July 2 (Phase 3) — runs through Andrew's OOO, no client dependency.
Parallel run, training, and cutover, July 7–16 (Phase 4) — timed for Andrew's return, with margin before July 20.

What Andrew needs to know (for Kim's intro and Joshua's messaging)

You have a team. Joshua (relationship and commercial), Kim (your day-to-day project manager), Denver (build and migration), Brendan (technical advisor).
Your data is being secured this week. After that, it does not matter what Kindful does or when — your data is safe with us.
We built the schedule around your time out (late June through the July 4 weekend). Nothing needs you while you're away.
You'll be live in FlintKit with room to spare before July 20.