Skip to content
Skipper
Onboarding

From demo to launch

Four steps take you from your current ticket system or shared mailbox to working in your own instance. We set up Skipper together with every business, and your customers keep writing to the same address.

Request a demo Hosting & licensing
Process

The process in four steps

  1. Demo

    We show you Skipper using your own workflows and work out together what changes compared with your current system.

  2. Choose a hosting option

    You decide whether we run your instance in the cloud or you host it yourself. We give you the price for your hosting option and the number of users in your team.

  3. Set up together

    We set up Skipper with you, including your mailbox and your integrations. You define activities, hourly rates and billing rules along the way.

  4. Enter your data and start

    You create your customers in Skipper, and we migrate tickets from your current system as agreed. From the cut-off date, your team works in Skipper.

Checklist

What you prepare

What to have ready for the joint setup. You only need the optional integrations if you use them.

  • Your mailbox

    • A support mailbox, for example a shared mailbox in Microsoft 365, in Google Workspace, on your Exchange server or via IMAP. Additional mailboxes per category as needed.
    • A person with administrator rights for your mailbox. We do the setup together. More about email and sign-in

  • Your team

    • The email address for your first administrator account.
    • Names and email addresses of your team members, and for each person their role (Administrator or Agent) and the ticket categories they should see.

  • Customers and billing

    • Project types and default projects, before you create customers: default projects are only created for newly added customers.
    • Your customers with their email domains, so that incoming requests are assigned to them.
    • Activities with hourly rates, different rates per customer, articles, travel-cost flat fees and locations.
    • Your billing rules: rounding, minimum times, VAT rate.
    • The next ticket number and a prefix, if you continue your existing number range.

  • Customer portal and emails

    • Company details and logo.
    • Legal notice and privacy policy for your customer portal: Skipper includes German templates with placeholders, which you fill in and have checked by a lawyer.
    • Your emails to customers in your own tone: confirmation email, signature, notifications. While you are at it, add the status page link to the confirmation email.

  • Optional integrations

  • Self-hosted only

    • A container environment on your server, PostgreSQL with the pgvector extension and S3-compatible storage for attachments, logos and images.
    • An SMTP account for your team’s sign-in links and a domain with a TLS certificate. More about self-hosted instances
Data migration

Your existing data

What we migrate, what you set up from scratch and what stays in your current system.

  • Customers and contacts

    How it gets into Skipper
    You create customers in Skipper with their email domains; for longer lists, we help during setup. Contacts are created automatically from incoming requests.

  • Tickets from your current system

    How it gets into Skipper
    We migrate your tickets from Zammad. If you are coming from another system, we work out the migration with you.

  • Ticket numbering

    How it gets into Skipper
    Can be continued: you set the next ticket number and, if you wish, a prefix. Without a migration, the old tickets stay in your current system.

  • Time entries

    How it gets into Skipper
    From a cut-off date, time is booked in Skipper. You bill anything before that as usual.

Questions about onboarding

Can I try Skipper first?

There is no test instance for trying Skipper out on your own. Instead, we show you Skipper in a demo and go through your workflows and questions. You request a demo through the contact form.

How does onboarding work?

After the demo, we set up Skipper together with you, including the connection to your Microsoft 365. During this, you create customers, contacts, activities with hourly rates and your billing rules in Skipper. You set up further integrations such as accounting, RMM, team chat or AI providers as needed, with your own accounts. Skipper is new on the market, and feedback from the first businesses goes directly into what we build next.

How does my existing data get into Skipper?

You create customers with their email domains in Skipper; for longer lists, we help during setup. Contacts are created automatically from incoming requests. We migrate tickets from Zammad; if you are coming from another ticket system, we work out the migration with you. You continue your ticket numbering, and your customers keep writing to the same address.

Can I continue my existing ticket numbering?

Yes. In sequential mode, you set the next ticket number, optionally with a prefix such as SUP. Skipper then continues counting where your previous system stopped. Without a migration, the old tickets stay in your previous system.

Start with a demo

Onboarding starts with a demo. We show you Skipper and go through what you need to prepare for the launch.

Request a demo