How migration requests work

A migration request is how you ask a verified partner to handle a switch for you. It bundles one or more switches (for example Mailchimp → Brevo and Google Analytics → Matomo), your urgency, and your goals. Once a partner takes it on, the request becomes a full project workspace: proposal, task tracking, configuration, messaging, and invoicing all live in one place under Requests.

There are two ways to start:

• From a partner — open the Partners page or any partner post and click “Request help”. The request goes directly to that partner.
• From your stack — request help based on My Stack, and the switches are built from the tools you have already mapped.

Add the switches you need, how urgent it is, and what you want to achieve. The more context you give — team size, data volumes, deadlines — the better the proposal you get back.

Every request moves through a clear pipeline. You can always see the current stage on the request card and inside the request detail page:

When the partner sends a proposal you get a notification, and the proposal appears on your request page. It covers the approach, the timeline, and the budget in DKK.

1. 1

   Read it through

   Check that the scope matches what you asked for. Use the conversation panel to ask questions before deciding.

2. 2

   Accept or decline

   Accept to move forward, or decline with a short reason. Declining is not the end — the partner can revise the proposal and send a new version.

3. 3

   Work begins

   After you accept, the partner clicks “Start work” and the project moves to In progress.

Most migrations need information only you have — account access, domain settings, export files. The partner sends you a configuration checklist, which appears on your request page as a form. Fill in each item and submit; the partner sees your answers instantly in their workspace.

Once work starts, the Progress tab on your request shows everything live, tracked by your partner:

• Workflow status — how many tasks are to-do, in progress, and done.
• Task list — every migration task, grouped by category, with priorities.
• Activity timeline — a chronological log of everything that happened: proposal sent, tasks completed, messages, invoices.

You can also manage per-project email updates, so important events reach your inbox even when you are not logged in.

Every request has its own conversation thread. Use it for anything about the project — it keeps the discussion attached to the migration so nothing gets lost. Both you and the partner are notified of new messages.

When the partner invoices you, the invoice appears on your request page with line items, tax, the total, a due date, and the partner’s bank details for the transfer.

1. 1

   Review the invoice

   It shows “Awaiting payment” with everything you need to pay by bank transfer.

2. 2

   Pay and confirm

   After you make the transfer, click “I’ve paid”. The partner is notified and confirms receipt on their side.

3. 3

   Done

   The invoice flips to Paid and stays on the project for your records.

When every task is done, the partner marks the project Completed. You will be invited to share your switching experience with the community — a pre-filled post with your switch and partner already attached. Your story helps the next business make the same move.