# Technical requirements: systems, data, access and owners

Handoff Checklist, item 7 of 12, read 10 Nov 2026

**The short answer.** Technical requirements are the systems, data, access and security steps the customer must provide before go-live. Moxo says it builds onboarding from forms, file requests, tasks and approvals, and OnRamp says a closed-won deal creates a project with deal-specific data pre-populated.

07

- **Who hands it over:** Sales engineer
- **When:** Before kickoff, with the buyer's technical owner named

## What passes

- The systems involved and their versions.
- The data to be loaded and who owns it.
- The access the delivery team needs, and by when.
- Security or legal steps the buyer must complete.
- The named technical owner on the buyer side.

## When it does not pass

The kickoff call finds that no one has asked the buyer's IT team for access, and a task that takes two days waits three weeks.

## Which portals carry it over

1 of 13 portals show this item carried over without re-entry: Trumpet; 3 in part.

| Portal | Carried over | Evidence |
| --- | --- | --- |
| [Flowla](/platforms/flowla/) |  partial | The onboarding page gives an example of "a security review flagged on the sales call" added as a plan step. ([source](https://www.flowla.com/customer-onboarding)) |
| [Dock](/platforms/dock/) |  none found | None found on 10 Nov 2026 in Dock's handoff guide, client portal page, onboarding page and integrations page: a statement that technical requirements carries from the deal into onboarding. ([source](https://www.dock.us/library/sales-to-customer-success-handoff)) |
| [Trumpet](/platforms/trumpet/) |  yes | The handover post lists "Technical requirements" among what the Pod already contains for the CSM. ([source](https://www.sendtrumpet.com/blog-posts/onboarding-starts-with-the-handover)) |
| [GetAccept](/platforms/getaccept/) |  partial | The template maps dependencies (security review, integrations, data migration) to action plan tasks with owners. ([source](https://www.getaccept.com/blog/sales-to-customer-success-handoff-process-with-digital-sales-rooms)) |
| [Aligned](/platforms/aligned/) |  none found | None found on 10 Nov 2026 in the home page, the onboarding software, client onboarding portal, Customer Success Hub and onboarding flow pages and the Zapier and Meetings tab help articles: a statement that technical requirements carries from the deal into onboarding. ([source](https://alignedup.com/customer-onboarding-software/?utm_source=whichclientportal.com&utm_medium=referral&utm_campaign=checklist)) |
| [Accord](/platforms/accord/) |  none found | None found on 10 Nov 2026 in the implementation page, the Assemble customer post and the digital sales room page: a statement that technical requirements carries from the deal into onboarding. ([source](https://inaccord.com/use-case/implementation)) |
| [HubSpot Sales Hub](/platforms/hubspot/) |  none found | None found on 10 Nov 2026 in the onboarding plans article, the deal plans article and the deal progression article: a statement that technical requirements carries from the deal into onboarding. ([source](https://knowledge.hubspot.com/customer-success/create-and-manage-customer-onboarding-plans)) |
| [GUIDEcx](/platforms/guidecx/) |  partial | The Salesforce page says templates are chosen accounting for the products, services and implementation requirements each customer brings. ([source](https://www.guidecx.com/products/integrations/salesforce/)) |
| [Rocketlane](/platforms/rocketlane/) |  none found | None found on 10 Nov 2026 in the HubSpot and Salesforce help articles and the integrations page (the HubSpot mapping lists deal name, owner, company, create and close dates and a template): a statement that technical requirements carries from the deal into onboarding. ([source](https://help.rocketlane.com/support/solutions/articles/67000715492-rocketlane-s-integration-for-hubspot)) |
| [Arrows](/platforms/arrows/) |  none found | None found on 10 Nov 2026 in the HubSpot onboarding story, the HubSpot acceleration story, the space-creation post and the sales room page: a statement that technical requirements carries from the deal into onboarding. ([source](https://arrows.to/resources/create-arrows-spaces/)) |
| [OnRamp](/platforms/onramp/) |  none found | None found on 10 Nov 2026 in the onboarding visibility page, the integrations page, the customer portal page and the handoff blog post: a statement that technical requirements carries from the deal into onboarding. ([source](https://onramp.ai/onboarding-visibility)) |
| [Moxo](/platforms/moxo/) |  none found | None found on 10 Nov 2026 in the customer onboarding page, the client portal page and the product page: a statement that technical requirements carries from the deal into onboarding. ([source](https://www.moxo.com/workflow/customer-onboarding)) |
| [Salesforce Sales Cloud](/platforms/salesforce/) |  none found | None found on 10 Nov 2026 in the Sales Cloud page, the Sales AI page and the revenue orchestration page: a statement that technical requirements carries from the deal into onboarding. ([source](https://www.salesforce.com/sales/)) |

## Sources

- Moxo: Vendor onboarding page says processes are built from forms, file requests, tasks, approvals and: https://www.moxo.com/workflow/customer-onboarding (read 10 Nov 2026)
- OnRamp: Vendor says a deal marked Closed Won in Salesforce or HubSpot creates a structured onboarding project with: https://onramp.ai/onboarding-visibility (read 10 Nov 2026)
- GUIDEcx: Vendor Salesforce page says Salesforce data selects the project, phase and milestone templates for each: https://www.guidecx.com/products/integrations/salesforce/ (read 10 Nov 2026)
- https://www.sendtrumpet.com/blog-posts/onboarding-starts-with-the-handover (read 10 Nov 2026)
- https://www.flowla.com/customer-onboarding (read 10 Nov 2026)
- https://www.getaccept.com/blog/sales-to-customer-success-handoff-process-with-digital-sales-rooms (read 10 Nov 2026)
- https://www.guidecx.com/products/integrations/salesforce/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://whichclientportal.com/checklist/technical-requirements/
