Browse all docs
Implementation & integrationsAdminImplementation

Implementation checklist

Move from kickoff through configuration, validation, and launch.

Updated July 22, 2026

1. Kickoff and ownership

  • Name the executive sponsor, implementation owner, IT owner, and workflow owners.
  • Agree on scope, success measures, decision dates, and the target go-live date.
  • Complete What we need from your company.
  • Establish a secure channel for credentials and restricted configuration material.

2. Workspace configuration

  • Approve company branding, default time zone, and enabled modules.
  • Document the lending stages, roles, approval paths, capital sources, and credit criteria.
  • Confirm which templates and exports need customer branding.
  • Identify any policy or workflow that must be resolved before users begin testing.

3. Identity and core connections

  • Configure the chosen identity provider and approved email domains.
  • Add a small pilot group with administrator and standard-user coverage.
  • Connect and test the deal intake mailbox.
  • Connect Slack if it is part of the approved launch scope.
  • Record owners and renewal dates for customer-managed applications or credentials.

4. Data preparation

  • Inventory source systems and nominate a source of truth for each record type.
  • Send representative, non-sensitive samples before the main data handoff.
  • Approve field mappings, duplicate rules, historical cutoff dates, and exception handling.
  • Load the agreed initial records and reconcile counts and key totals.

5. Validation and training

  • Run an opportunity from email intake through deal review and underwriting.
  • Test access for an administrator, a standard user, and a blocked user.
  • Verify documents, notifications, branded outputs, and exports.
  • Train each team on the workflows and modules it will actually use.
  • Record defects, assign owners, and retest resolved items.

6. Launch and handoff

  • Complete the go-live checklist.
  • Approve the production launch and any final data cutoff.
  • Confirm support contacts, escalation paths, and configuration-change authority.
  • Schedule the first adoption and data-quality review after launch.

Your implementation lead should keep this checklist as the shared launch record and identify the owner and evidence for every completed item.