ActiveCampaign Migration — Phase 1.5 Restore-Test Runbook

0. Ground rule

This is not a production import.

Do not restore into live ActiveCampaign, live Supabase production tables, live GoHighLevel production records, or any system currently sending email or running automations.

Restore only into a quarantined test destination.

1. Inputs required

Local archive

Manifest

Use the completed Phase 1 export set as the fixed source snapshot for the restore test.

2. Restore destination options

3. Restore folder structure

Create a dedicated restore workspace:

mkdir -p /root/.openclaw/workspace/Restores/activecampaign-migration-restore-test-2026-04-22/{source,working,sql,reports}

Copy the export set into source so the test runs on a fixed snapshot:

cp -R /root/.openclaw/workspace/Exports/activecampaign-migration-2026-04-22/* \
  /root/.openclaw/workspace/Restores/activecampaign-migration-restore-test-2026-04-22/source/

Create the report file:

touch /root/.openclaw/workspace/Restores/activecampaign-migration-restore-test-2026-04-22/reports/restore-test-report-2026-04-22.md

4. Expected baseline counts

The manifest is the source of truth. Current expected values are:

5. Restore-test scope

This phase is about proof, not perfect production recreation.

• Files are readable
• Files load into a clean destination
• Counts survive import
• Core fields survive import
• Suppression / unsubscribe state survives import
• Known sample records still match

6. Restore procedure

6.1 Verify source files before import

find /root/.openclaw/workspace/Restores/activecampaign-migration-restore-test-2026-04-22/source -type f | sort

head -n 3 /root/.openclaw/workspace/Restores/activecampaign-migration-restore-test-2026-04-22/source/activecampaign/ac-contacts-2026-04-22.csv
head -n 3 /root/.openclaw/workspace/Restores/activecampaign-migration-restore-test-2026-04-22/source/supabase/supabase-purchases-2026-04-22.csv
head -n 3 /root/.openclaw/workspace/Restores/activecampaign-migration-restore-test-2026-04-22/source/payments/stripe-payments-2026-04-22.csv

Stop immediately if files are missing, malformed, truncated, or headerless.

6.2 Create restore tables

Minimum restore tables:

• restore_ac_contacts
• restore_ac_tags
• restore_ac_unsubscribes
• restore_sb_contacts
• restore_sb_purchases
• restore_sb_email_suppressions
• restore_sb_leads
• restore_stripe_customers
• restore_stripe_payments
• restore_paypal_transactions

If using PostgreSQL directly:

\copy restore_ac_contacts FROM '/absolute/path/to/ac-contacts-2026-04-22.csv' CSV HEADER;

6.3 Load suppression data early

Restore these first:

• ac-unsubscribes-2026-04-22.csv
• supabase-email-suppressions-2026-04-22.csv

If suppression state fails, pause the whole restore test.

7. Validation checks

7.1 Row-count reconciliation

| dataset | expected | restored | pass/fail | notes |
|---|---:|---:|---|---|
| ac_contacts | 25935 |  |  |  |
| ac_tags | 112 |  |  |  |
| ac_unsubscribes | 81 |  |  |  |
| sb_contacts | 195 |  |  |  |
| sb_purchases | 195 |  |  |  |
| sb_email_suppressions | 1 |  |  |  |
| sb_leads | 198 |  |  |  |
| stripe_customers | 4639 |  |  |  |
| stripe_payments | 33368 |  |  |  |
| paypal_transactions | 5964 |  |  |  |

7.2 Sample-record verification

Check at least 5 records total:

• 2 ActiveCampaign contacts
• 1 Supabase contact
• 1 Supabase purchase
• 1 suppression / unsubscribe record

7.3 Suppression survival test

This is mandatory. Prove at least one AC unsubscribe row and one Supabase suppression row survive the restore with state intact.

7.4 Purchase continuity test

Prove at least one purchaser can still be traced through contact identity, purchase row, and payment evidence where available.

8. Restore-test report template

# Restore Test Report — 2026-04-22

## Destination
- type:
- environment:
- isolated from production: yes / no

## Source archive used
- local path:
- manifest path:

## Row-count reconciliation
| dataset | expected | restored | pass/fail | notes |
|---|---:|---:|---|---|

## Sample-record checks
- sample 1:
- sample 2:
- sample 3:
- sample 4:
- sample 5:

## Suppression verification
- AC unsubscribe restored:
- Supabase suppression restored:
- result:

## Issues found
-

## Final verdict
- PASS / FAIL / PASS WITH WARNINGS

## Recommendation
- safe to proceed to migration planning: yes / no

9. Pass / fail rules

10. Stop conditions

• Malformed CSV
• Restored counts materially differ from manifest
• Unsubscribe data cannot be restored cleanly
• Imported data triggers live integrations
• Destination is not clearly isolated from production

Do not continue to broader migration until these are resolved.

11. Recommendation after Phase 1.5

If restore test passes:

1. freeze the validated archive set
2. preserve the restore-test report with the manifest
3. move into migration mapping and staged cutover planning
4. keep ActiveCampaign live until staged reconciliation is complete

If restore test fails:

1. document the failure clearly
2. fix the archive or restore process
3. rerun Phase 1.5
4. do not proceed to decommissioning decisions

A backup is not proven until it restores.