Docs

Migrating from Keitaro

Orbitra transfers settings from Keitaro β€” affiliate networks, offers, domains, campaigns with their Click API tokens, streams with filters, campaign postbacks, landing pages, and sources. Click statistics are not transferred: this is a fresh start.

What gets transferred

KeitaroOrbitraWhat is preserved
Affiliate networksAffiliate networksPostback URL, offer parameters
OffersOffersURL, payout, geo
DomainsDomainsParking, HTTPS-only
GroupsCampaign groupsName
CampaignsCampaignsAlias, Click API token, state, source
StreamsStreamsType, position, weight, schema, action, filters (including sub_id_N and parameter filters), "allow / deny" modes, associations with offers and landing pages
Campaign postbacksS2S PostbacksURL, method, statuses
Landing pagesLanding pagesNames and URLs
SourcesSourcesParameters

Not transferred: clicks and conversions, users, local landing files (only records about them). Filters that cannot be transferred are listed in the import report.

Keitaro's source and affiliate-network templates are already built into Orbitra β€” there is no need to transfer them (Traffic sources and affiliate networks).

1. Dump on the Keitaro server

Connect to the Keitaro server over SSH as root and run the command in its entirety. It takes database credentials from /etc/keitaro/env/inventory.env, works both with a MariaDB client on the host and with MariaDB inside a Keitaro Docker container, dumps only the settings tables (no click logs), and refuses to run if the tables are not found β€” so you never accidentally dump the whole database.

bash <<'ORBITRA_DUMP'
set -eo pipefail

# Sourced before set -u: the env file is Keitaro's, not ours.
source /etc/keitaro/env/inventory.env
set -u

# Password goes through the environment, never through argv or a file left on disk.
export MYSQL_PWD="$MARIADB_KEITARO_PASSWORD"
DB="$MARIADB_KEITARO_DATABASE"

# MariaDB client on the host, or inside the Keitaro MariaDB container.
if CLI=$(command -v mariadb || command -v mysql) && DUMP=$(command -v mariadb-dump || command -v mysqldump); then
  sql()  { "$CLI"  -u"$MARIADB_KEITARO_USER" -h127.0.0.1 -P3306 --protocol=tcp "$@" </dev/null; }
  dump() { "$DUMP" -u"$MARIADB_KEITARO_USER" -h127.0.0.1 -P3306 --protocol=tcp "$@" </dev/null; }
else
  CT=$(docker ps --format '{{.Names}}' 2>/dev/null | grep -i -m1 -E 'mariadb|mysql' || true)
  if [ -z "$CT" ]; then
    echo "ERROR: no MariaDB client on this server and no MariaDB container found" >&2
    exit 1
  fi
  echo "Using MariaDB inside container: $CT"
  sql()  { docker exec -e MYSQL_PWD "$CT" sh -c 'exec $(command -v mariadb || command -v mysql) "$@"' sh -u"$MARIADB_KEITARO_USER" "$@" </dev/null; }
  dump() { docker exec -e MYSQL_PWD "$CT" sh -c 'exec $(command -v mariadb-dump || command -v mysqldump) "$@"' sh -u"$MARIADB_KEITARO_USER" "$@" </dev/null; }
fi

# Settings tables only: campaigns, offers, domains, streams... - no click logs.
TABLES=$(sql -N "$DB" -e "
SELECT table_name FROM information_schema.tables
WHERE table_schema = DATABASE()
  AND table_name IN (
    'keitaro_affiliate_networks', 'keitaro_groups', 'keitaro_offers',
    'keitaro_domains', 'keitaro_campaigns', 'keitaro_campaign_postbacks',
    'keitaro_landings', 'keitaro_streams', 'keitaro_stream_filters',
    'keitaro_stream_offer_associations', 'keitaro_stream_landing_associations',
    'keitaro_traffic_sources', 'keitaro_ref_sources')
ORDER BY table_name" | tr '\n' ' ')

# Without a table list mysqldump would dump the WHOLE database, click logs included.
if [ -z "$(echo $TABLES)" ]; then
  echo "ERROR: no Keitaro tables found in database $DB" >&2
  exit 1
fi

OUT=/root/keitaro_orbitra_full.sql.gz
echo "Dumping tables: $TABLES"
dump --single-transaction --quick --skip-lock-tables "$DB" $TABLES | gzip -1 > "$OUT"

ls -lah "$OUT"
echo "DONE: $OUT"
ORBITRA_DUMP

At the end you will see DONE: /root/keitaro_orbitra_full.sql.gz. The file is usually 1–5 MB.

2. Download the file

On the βš™ β†’ Migrations page, enter the Keitaro server's IP β€” the panel will fill it into ready-made commands. Run the command on your computer, not on the server:

# macOS / Linux
scp root@IP_KEITARO:/root/keitaro_orbitra_full.sql.gz ~/Downloads/
# Windows (PowerShell)
scp root@IP_KEITARO:/root/keitaro_orbitra_full.sql.gz $env:USERPROFILE\Downloads\

3. Import into Orbitra

βš™ β†’ Migrations β†’ Import from Keitaro (SQL dump):

  1. Choose a .sql.gz or .sql file. The dump is not executed as SQL β€” it is only parsed.
  2. Check what to import. Keep campaign IDs (Orbitra ID = Keitaro ID) only works on a clean installation where the campaign table is empty, including the archive.
  3. Show preview β€” a dry run without writing: how many objects of each type will be imported and which filters do not transfer.
  4. Import into Orbitra.

For repeated imports on a test server there is a Cleanup block: it deletes the tracker's entire configuration (domains, offers, affiliate networks, campaigns, streams, postbacks, pixels, sources, landing pages, groups) without touching statistics or users. You must type DELETE to confirm.

4. After the import

Common problems

SymptomCause and solution
The dump command says no Keitaro tables foundWrong database in inventory.env or a non-standard Keitaro installation. Check MARIADB_KEITARO_DATABASE
no MariaDB client … and no MariaDB container foundNo MariaDB client and no running MariaDB container β€” start Keitaro or install the client
The import found nothingThe dump is empty or from the wrong database β€” check the file size and the Dumping tables: line in the command output
Streams were not transferredThe "Import streams" option was not checked, or the dump lacks keitaro_streams and the association tables
The domain answers 404DNS does not point at the new server yet, or the domain has no Index campaign assigned
← Previous
Installation and updates
Next β†’
Migrating from Binom
View source on GitHub: github.com/fenjo26/Orbitra.link/wiki
All guides
Docs

Quick start: your first campaign

The short path: install the tracker, create a campaign, and get your first clicks and conversions in under an hour.

Read guide β†’
Docs

Installation and updates

Install Orbitra on a fresh Ubuntu or Debian server with one command, and update to new versions safely.

Read guide β†’
Docs

Migrating from Keitaro

Move campaigns, offers, sources and domains from Keitaro to Orbitra in one click β€” what transfers and what to check.

Read guide β†’
Docs

Migrating from Binom

Move campaigns and streams from Binom to Orbitra: what transfers automatically and what to set up by hand.

Read guide β†’
Docs

Feature overview

Everything Orbitra can do: campaigns and streams, cloaking, landings, PWA, postbacks, costs, reports and integrations.

Read guide β†’
Docs

Campaigns and streams

The complete reference: campaign settings, stream types, schemas, rotation, filters, test links and every option explained.

Read guide β†’
Docs

Cloaking

Full cloaking reference: detection layers, global settings, per-stream filters, verdicts and reports.

Read guide β†’
Docs

Browser check

How the JS check catches bots, VMs and emulators through contradictions in the browser environment.

Read guide β†’
Docs

Landing pages

Landing types, the {offer} macro, the JS adapter, LeadForge and multi-offer landings β€” the complete reference.

Read guide β†’
Docs

PWA and Web Push

Build installable PWA apps and collect push subscribers: settings, icons, events and notifications.

Read guide β†’
Docs

PWA Funnel

A multi-step PWA funnel: install prompts, event tracking and re-engagement notifications.

Read guide β†’
Docs

Conversion popups

Show real conversion events as on-page popups: setup, triggers and placement.

Read guide β†’
Docs

Session recordings and heatmaps

Replay real visits and see click and scroll maps. Storage limits and privacy notes.

Read guide β†’
Docs

Content gallery

Central storage for icons, screenshots and creatives used across PWAs and landings.

Read guide β†’
Docs

Creatives library

Store creatives with subid tracking and test them across campaigns.

Read guide β†’
Docs

External PWA and Telegram channels

Publish PWAs to external domains and run Telegram channels as a traffic source.

Read guide β†’
Docs

Postbacks and conversions

Incoming postbacks, conversion statuses and types, and outgoing S2S postbacks to your traffic source.

Read guide β†’
Docs

Costs

Import spend from Facebook, TikTok and Google Ads, or update it via API and cron β€” and how the revenue aggregator works.

Read guide β†’
Docs

Push and pop networks

Working with push and pop traffic sources: feeds, zone optimization and the zone killer.

Read guide β†’
Docs

Facebook / Meta

Cost import from Meta Ads and the Conversions API: server-side events with deduplication.

Read guide β†’
Docs

Dolphin / Fbtool

Receive Facebook costs through the Dolphin (Fbtool) API in real time.

Read guide β†’
Docs

FB comment cleaner

Bulk-moderate comments under Meta ads: hide, delete and filter by keywords.

Read guide β†’
Docs

Traffic sources and affiliate networks

Catalog of 50+ traffic sources and 440+ networks: templates, parameters and postback URLs.

Read guide β†’
Docs

Reports, logs and metrics

The report builder, saved reports, click logs and every metric explained.

Read guide β†’
Docs

Domains and SSL

Add domains, DNS, free Let's Encrypt certificates, redirects, parking and every switch on the page.

Read guide β†’
Docs

Cloudflare

How to run campaign domains through Cloudflare: DNS, SSL modes and what to turn off.

Read guide β†’
Docs

Administration

Users, roles and permissions, security settings, geo databases, updates and system health.

Read guide β†’
Docs

Telegram bot

Manage the tracker from Telegram: stats, conversions and alerts in chat.

Read guide β†’
Docs

MCP: an AI assistant in the tracker

Connect Claude or any MCP client to Orbitra and manage campaigns with plain-language commands.

Read guide β†’