Skip to content
Back to guides
Guide

Migrate from GoPhish to a SaaS phishing simulation platform (2026 guide)

Move from GoPhish to a hosted platform: export groups with the API, import a CSV or sync Microsoft 365, convert template variables, archive results. Updated November 18, 2026.

Thomas Ferreira 11 min read

To migrate from GoPhish to a SaaS phishing simulation platform, you move three things by file: the people (a CSV rebuilt from the GoPhish API, or a directory sync), your own templates (HTML pasted after converting the variables), and the campaign history (GoPhish CSV exports kept as an archive). Then you swap the allow-list entries in your mail system and shut the server down. This guide walks through each step with nophi.sh as the target.

Updated November 18, 2026. The commands were checked against GoPhish 0.12.1, the latest release (14 September 2022). They use the GoPhish REST API, which GoPhish describes as the base of its interface: “the UI is just a wrapper around a powerful JSON RESTful API”.

Why teams migrate off GoPhish in 2026

GoPhish still works, but nobody ships it any more. The latest release is v0.12.1 of 14 September 2022, the main branch has had no commit since 23 September 2024, and its creator wrote that same month that “Gophish is essentially in maintenance mode” (issue #3234). On 18 November 2026, the repository had 676 open issues and 84 open pull requests. NVD lists twelve CVEs against 0.12.1, published between March 2023 and October 2026, and no release fixes them.

Community forks exist. The most active maintenance fork we found, raginx/gophish-ng, was created in July 2026 and describes itself as “an actively maintained fork of Gophish”, with a newer Go toolchain and security fixes. It is a separate project with its own maintainers, not a GoPhish release. Other well-known forks (evilgophish, kgretzky/gophish) target red-team work with Evilginx rather than awareness programmes.

For a one-off test, that may not matter. For a programme that runs all year, the server, its patches, the deliverability work and the reporting take more time than the campaigns. That is when a hosted platform starts to pay off.

Take stock of your instance

Start by measuring what you have. From the server, or through an SSH tunnel to the admin port:

export GOPHISH_URL="https://127.0.0.1:3333"
export GOPHISH_API_KEY="key-from-the-settings-page"
H="Authorization: Bearer $GOPHISH_API_KEY"

curl -sk -H "$H" "$GOPHISH_URL/api/groups/" \
  | jq '{groups: length, targets: ([.[].targets[].email | ascii_downcase] | unique | length)}'
curl -sk -H "$H" "$GOPHISH_URL/api/templates/" | jq 'map(.name)'
curl -sk -H "$H" "$GOPHISH_URL/api/campaigns/summary" \
  | jq '.campaigns[] | {id, name, status, launch_date}'

The first call counts each person once, even when they sit in several groups. The template list tells you which ones are worth bringing over. The campaigns listed are the ones to export before you switch the server off.

Step 1: export the targets

The “Users & Groups” page of GoPhish imports a CSV (“Bulk Import Users”) and offers a template file, but it has no export button. Reuse the original CSV (the HR export that built the groups), or rebuild it from the API.

GoPhish stores four fields per person: email, first_name, last_name and position. If you filled position with the department, this command writes a CSV ready to import, one row per address:

curl -sk -H "$H" "$GOPHISH_URL/api/groups/" \
| jq -r '["email","first_name","last_name","department"],
         ([.[].targets[]] | unique_by(.email | ascii_downcase) | .[]
          | [.email, .first_name, .last_name, .position])
         | @csv' > targets.csv

If your GoPhish groups matched departments (“Finance”, “Management”), use the group name as the department instead:

curl -sk -H "$H" "$GOPHISH_URL/api/groups/" \
| jq -r '["email","first_name","last_name","department"],
         ([.[] | .name as $g | .targets[] | [.email, .first_name, .last_name, $g]]
          | unique_by(.[0] | ascii_downcase) | .[])
         | @csv' > targets.csv

A person who appears in two groups is kept once, with the department of the first group that contains them. Check those cases by hand if your groups overlap.

Step 2: import the people into nophi.sh

Three ways in, depending on your directory.

Import a CSV file, on the people page. Only email is required; first_name, last_name, department, manager_email and phone are optional. Comma, semicolon and tab separators are accepted, with English or French headers. A file that comes straight from GoPhish works: the First Name, Last Name and Email headers are recognised. The Position column is not used, so rename it department if it holds the department. Addresses already in the list are skipped.

Paste a list of addresses, copied from Outlook, Excel or Google Sheets, for a small team or a pilot group.

Sync Microsoft 365 (Entra ID). It needs an app registration in Entra ID with the Microsoft Graph permission User.Read.All, then brings accounts with their department and manager from the directory.

One change of model to plan for: each person belongs to a department, and a campaign targets the whole organisation, a department, a risk level or a selection of people. Your GoPhish groups therefore become departments, or selections when you launch a campaign.

Step 3: bring over your templates

Before converting anything, browse the included library: 135 ready-made scenarios, 69 in French and 66 in English, with three difficulty levels (CEO fraud, supplier bank-detail change, invoices, Microsoft 365, Teams and SharePoint, IT support, HR, delivery, government, QR codes and more). Some of your GoPhish templates probably have an equivalent already.

For the ones that are yours, export them from GoPhish first. This script writes each template’s HTML to a file and keeps the subject and sender in an index:

import json
import os
import re
import unicodedata
from pathlib import Path

import requests

URL = os.environ["GOPHISH_URL"].rstrip("/")
r = requests.get(f"{URL}/api/templates/",
                 headers={"Authorization": f"Bearer {os.environ['GOPHISH_API_KEY']}"},
                 verify=os.environ.get("GOPHISH_VERIFY_TLS", "1") != "0",
                 allow_redirects=False, timeout=30)
r.raise_for_status()

folder = Path("gophish-templates")
folder.mkdir(exist_ok=True)
index = []
for t in r.json():
    ascii_name = unicodedata.normalize("NFKD", t["name"]).encode("ascii", "ignore")
    slug = re.sub(r"[^a-z0-9]+", "-", ascii_name.decode().lower()).strip("-")
    filename = f"{t['id']:03d}-{slug}.html"
    (folder / filename).write_text(t["html"], encoding="utf-8")
    index.append({"file": filename, "name": t["name"], "subject": t["subject"],
                  "sender": t["envelope_sender"],
                  "attachments": len(t["attachments"])})

(folder / "index.json").write_text(json.dumps(index, indent=2), encoding="utf-8")

Then convert the variables. nophi.sh uses plain merge fields, with no logic:

GoPhishnophi.shNote
{{.FirstName}}{{first_name}}
{{.LastName}}{{last_name}}
{{.Email}}{{email}}
{{.Position}}{{department}}if Position held the department
{{.URL}}{{phishing_link}}tracked link to the simulation page
{{.Tracker}}{{tracking_pixel}}open-tracking pixel
{{.From}}, {{.RId}}, {{.TrackingURL}}, {{.BaseURL}}noneremove
none{{company_name}}, {{company_domain}}your organisation’s name and e-mail domain
none{{qr_code}}QR code of the tracked link

The six common variables convert with one sed command. It tolerates the spaces Go accepts inside the braces:

sed -E \
  -e 's/\{\{ *\.FirstName *\}\}/{{first_name}}/g' \
  -e 's/\{\{ *\.LastName *\}\}/{{last_name}}/g' \
  -e 's/\{\{ *\.Email *\}\}/{{email}}/g' \
  -e 's/\{\{ *\.Position *\}\}/{{department}}/g' \
  -e 's/\{\{ *\.URL *\}\}/{{phishing_link}}/g' \
  -e 's/\{\{ *\.Tracker *\}\}/{{tracking_pixel}}/g' \
  gophish-templates/012-internal-memo.html > internal-memo-nophish.html

# Check: list the fields left between braces
grep -o '{{[^}]*}}' internal-memo-nophish.html | sort | uniq -c

Go conditions ({{if .FirstName}}...{{end}}) have no equivalent: replace them with fixed text. The final check lists every field left between braces; only nophi.sh fields should remain.

In nophi.sh, open “Create a template”. The form asks for the template name, category, difficulty, language, sender name and e-mail, subject, Body HTML (the source pastes as it is), a plain-text version and the clues. Two differences from GoPhish:

  • the sender address is the part before the @: the domain is always the sending domain set up with you, which replaces both the template’s Envelope Sender and the GoPhish SMTP From;
  • the clues (what should have alerted the person: sender, subject, link, content) feed the debrief shown right after a click. Take the time to write them.

Check each template with “Preview” before you use it.

Step 4: landing pages and submitted data

In GoPhish you built landing pages, with or without capturing what was typed. In nophi.sh, scenarios use fake sign-in pages for Microsoft 365, Google Workspace or a generic portal, and passwords typed there are never collected: the password field is never sent by the browser. The person who clicks sees a debrief of the clues they missed, then gets a short course assigned automatically, with reminders before the due date and an alert to their manager after it.

Whatever your GoPhish landing pages captured stays in the gophish.db database. It belongs to step 6.

Step 5: sending and the allow-list

You no longer maintain a sending profile. Simulations leave from nophi.sh’s infrastructure, from an authenticated sending domain (SPF, DKIM and DMARC aligned). SMTP relays, quotas and DKIM signing are no longer your problem.

The allow-listing in your mail system still has to be done. The console shows the exact values in Settings, Sending simulations, detects your mail provider from your MX records and sends a real test e-mail through the simulation path, with an “I received this email” button to confirm delivery. On Microsoft 365, add the nophi.sh sending domain and IP addresses to the Advanced Delivery policy, Phishing simulation tab; our Microsoft 365 Advanced Delivery guide gives every field and the PowerShell for IPv6. On Google Workspace, follow our Google Workspace allow-list guide. Once the migration is done, remove your GoPhish entries: a filtering exception that no longer serves has no reason to stay.

Reporting changes too. GoPhish reads reports from an IMAP mailbox (since version 0.9.0). With nophi.sh, employees use the nophi.sh report button in Outlook or Gmail, or forward the suspicious e-mail to the nophi.sh address. They get an AI verdict with its reasons, usually in one to two minutes, and your security contacts are alerted.

Step 6: archive, then shut down GoPhish

nophi.sh measures from your first campaign. Before you switch GoPhish off, export what you need as evidence:

  • for each campaign, the “Export CSV” button on the results page offers “Results” (one row per person) and “Raw Events” (the full timeline) (GoPhish documentation);
  • by script, GET /api/campaigns/:id/results returns the same data as JSON.

Then clean up in this order:

  1. delete the campaigns once exported (DELETE /api/campaigns/:id also erases their results and timeline), or the whole database, according to the retention period in your GDPR record;
  2. revoke the API key and the GoPhish accounts;
  3. stop the service, then destroy the server and its backups once the retention period has passed;
  4. remove the DNS records of the admin and phishing subdomains, and the GoPhish entries from your allow-lists.

What changes day to day

Once you have switched, the tasks you scripted around GoPhish move into the product:

  • campaigns relaunch on their own according to each person’s risk level (every 7, 14 or 30 days), during working hours, with staggered sending;
  • the dashboard follows a risk score per person and per department, repeat clickers, people never tested and overdue training;
  • the open, click and submit funnel reads per campaign, and the PDF audit report and CSV export serve as evidence for NIS2, ISO 27001 (A.6.3) or DORA audits;
  • data is hosted in France.

How it works end to end is on the phishing simulation page, and the GoPhish comparison sets out the gap point by point, with an estimate of what GoPhish really costs to run.

Run both in parallel before you switch off

Nothing forces a big-bang switch. The 14-day trial gives access to the full product, with no card. Import one department, run a nophi.sh campaign for it while GoPhish keeps going for the others, compare, then shut the server down. After the trial, nophi.sh costs €1 per person per month excl. VAT, everything included, with a minimum of 10 people, billed monthly with no commitment; details on the pricing page.

FAQ

Can I import GoPhish campaigns, templates and groups into a SaaS platform?

Yes, through files. Groups become a CSV of people (or a Microsoft 365 / Entra ID sync), templates are pasted as HTML after converting the variables, and campaign results stay in your archive as GoPhish CSV exports. GoPhish 0.12.1 has a JSON API for all three, which is the simplest way to extract them.

Do my GoPhish templates work as they are in nophi.sh?

The HTML pastes as it is into the Body HTML field, but the variables change: {{.FirstName}} becomes {{first_name}}, {{.URL}} becomes {{phishing_link}}, {{.Tracker}} becomes {{tracking_pixel}}. Go conditions ({{if}}...{{end}}) and the variables {{.RId}}, {{.From}}, {{.TrackingURL}} or {{.BaseURL}} are removed.

What happens to my GoPhish groups?

In nophi.sh, each person belongs to a department. If your GoPhish groups matched departments, use the group name as the department column when you export. A campaign can then target the whole organisation, a department, a risk level or a selection of people.

Can I keep the history of my GoPhish campaigns?

Yes, as an archive. Export each campaign with the “Export CSV” button on the results page (Results and Raw Events) or with GET /api/campaigns/:id/results, and keep the files according to your retention policy. nophi.sh measures from your first campaign.

Is GoPhish still maintained in 2026?

Barely. The latest release, v0.12.1, dates from 14 September 2022 and the latest commit on the main branch from 23 September 2024. In September 2024 its creator wrote that GoPhish is “essentially in maintenance mode”. The repository is not archived (checked on GitHub on 18 November 2026).

Do I need to change the Microsoft 365 allow-list?

Yes. Add the nophi.sh sending domain and IP addresses to the Advanced Delivery policy (Phishing simulation tab), as described in our Microsoft 365 guide, then remove the entries of your GoPhish server once the migration is done.