P3CL — Backup & Restore Tool

⚙️

Settings & Secrets Backup

Exports your Supabase connection, API keys, email config, and custom templates to a JSON file you can store safely.

To restore on a new device or after clearing browser data:

Select settings backup file (.json)

💾

Local Data Backup (IndexedDB)

Exports all locally cached data — projects, estimates, clients, procurement orders, messages, and more — to a JSON file.

⚠️ This is your device's local cache. For the authoritative backup, use Supabase (see below).

Select local data backup file (.json)

☁️

Supabase Database Backup — Step-by-Step

Your Supabase database is the authoritative source of all data. Back it up regularly using the Supabase dashboard.

Method A — SQL Dump (Recommended)

1

Go to supabase.com → your project → Database → Backups

2

On free plan: click Download next to any listed backup (Supabase keeps 7 days of daily backups on paid plans; free plan: use the SQL Editor export below)

3

Free plan alternative: SQL Editor → run the query below → copy results → save as .sql file

-- Run in Supabase SQL Editor
-- Copy the result and save as a .sql file

SELECT 'INSERT INTO clients ' || row_to_json(t)::text FROM clients t;
SELECT 'INSERT INTO projects ' || row_to_json(t)::text FROM projects t;
SELECT 'INSERT INTO estimates ' || row_to_json(t)::text FROM estimates t;
SELECT 'INSERT INTO tasks ' || row_to_json(t)::text FROM tasks t;
SELECT 'INSERT INTO procurement_orders ' || row_to_json(t)::text FROM procurement_orders t;
SELECT 'INSERT INTO materials ' || row_to_json(t)::text FROM materials t;
SELECT 'INSERT INTO rates ' || row_to_json(t)::text FROM rates t;
SELECT 'INSERT INTO notes ' || row_to_json(t)::text FROM notes t;
SELECT 'INSERT INTO messages ' || row_to_json(t)::text FROM messages t;
SELECT 'INSERT INTO user_profiles ' || row_to_json(t)::text FROM user_profiles t;

Method B — Table Editor CSV Export

For each table you want to back up:

1. Supabase → Table Editor
2. Click the table name (e.g. clients)
3. Click the Export button (top right)
4. Choose CSV or JSON
5. Save the file with the table name

Tables to export:

clients projects estimates tasks procurement_orders materials rates notes messages user_profiles

💡 Paid Supabase plan tip: On the Pro plan ($25/mo) Supabase keeps 7 days of automatic point-in-time daily backups and lets you download them as .sql.gz files from the Backups section. This is the easiest option and takes one click.

🐙

GitHub Code Backup — Permanent Version Control

GitHub stores your complete platform code with a full history of every change. Free. Unlimited. If your laptop dies, Netlify burns down, or you need to roll back a bad update — GitHub has everything.

First-Time Setup (one-off)

1. Go to github.com → sign up (free)
2. Click + New repository
3. Name it p3cl-platform
4. Set to Private (your code stays yours)
5. Do NOT tick "Add README"
6. Click Create repository
7. Install Git on your computer: git-scm.com
8. Unzip p3cl-deploy.zip to a folder

Push your code to GitHub

Open Terminal (Mac/Linux) or Git Bash (Windows) and run:

cd path/to/p3cl-folder

git init
git add .
git commit -m "P3CL Platform v1.0"

# Replace YOUR_USERNAME with your GitHub username
git remote add origin https://github.com/YOUR_USERNAME/p3cl-platform.git
git branch -M main
git push -u origin main

After every update

Each time you get a new p3cl-deploy.zip, copy the files over and run:

git add .
git commit -m "Platform update $(date +%Y-%m-%d)"
git push

Connect Netlify to GitHub (auto-deploy)

Once connected, pushing to GitHub automatically deploys to Netlify:
1. Netlify → Site configuration → Build & deploy
2. Click Link to Git provider → GitHub
3. Select your p3cl-platform repo
4. Branch: main, Publish dir: leave blank
5. Click Deploy site
Now every git push goes live automatically.

⚠️ Never commit secrets to GitHub. The platform code itself contains no secrets — API keys and Supabase credentials are stored in your browser's localStorage, not in any file. The p3cl-deploy.zip is safe to push to GitHub as-is.

🔄

Full Platform Restore — Step by Step

Follow these steps to restore the complete platform after a catastrophic failure (lost device, account lockout, accidental deletion, etc.).

Step 1 — Restore the code

If you have GitHub:
• Download the repo as ZIP from GitHub
• Or: git clone https://github.com/YOU/p3cl-platform.git

If you have the ZIP backup only:
• Drag p3cl-deploy.zip to Netlify

Step 2 — Restore the database

In Supabase SQL Editor:
• Run SUPABASE_SCHEMA.sql first (creates all tables)
• Then paste and run your saved SQL dump

If you have CSV exports:
• Table Editor → Import → select each CSV file per table

Step 3 — Restore secrets

Open the platform URL in Chrome → open this Backup Tool → Restore Settings from File → select your settings .json backup

Or enter manually in Settings:
• Supabase URL + anon key
• Resend API key
• AI API key (OpenRouter/Anthropic)

Step 4 — Verify

• Sync dot → Setup → Test Connection → should show all 13 tables green
• Settings → Email → Send Test Email
• Material Pricing → AI Search → test a query
• Team Chat → send a test message
• Check dashboard shows your data

📅

Recommended Backup Schedule

Frequency	What	How	Time
Daily	Supabase auto-backup	Automatic on Pro plan ($25/mo). Free plan: manual SQL dump weekly.	0 min (auto)
Weekly	Code push to GitHub	`git add . && git commit -m "weekly backup" && git push`	2 min
Monthly	Settings + full data export	Use this tool → Export Settings + Export Local Data → save to cloud drive.	5 min
After every update	New code ZIP + schema	Push updated ZIP to GitHub immediately after deploying to Netlify.	2 min

💡 Where to store backup files: Google Drive, Dropbox, or OneDrive. Create a folder called P3CL Backups with subfolders: Database, Settings, LocalData. Name files with the date: p3cl-settings-2025-06-15.json

🛡️ P3CL Backup & Restore Tool