What onboarding sets up
Onboarding brings your product into the platform: Swapps reviews the current product, collects context, configures access, and prepares the support workflow. It is not a rebuild — it makes the existing product understandable and supportable.
Access and credentials to gather
- Hosting, server, or platform access
- Code repository access
- Domain and DNS management
- Third-party tools and integration credentials
- Analytics and monitoring access
Context to share
- A short product overview and its goals
- Key user flows and critical features
- Known issues, risks, or fragile areas
- Integrations and external services in use
- Environments (production, staging) and how to reach them
- Any existing documentation or runbooks
People and decisions
- Main point of contact for support
- Who approves changes and deployments
- Escalation path for urgent issues
- Internal stakeholders to keep informed
What to expect by tier
Setup effort scales with complexity: lighter for Build (simple sites), more for Launch (database, users, backend), and most for Scale (integrations, jobs, external services). Larger migrations may be scoped as a separate project or require a higher tier.