BECCASAUTORental Data Ops
Refresh

Beccas site transfer

Move Scraped Records To The Live Site

This page explains how clean scraper records from this operations database should be prepared, mapped, and transferred into the Beccas site Supabase project.

Transfer Records Now

Copy reviewed scraper records into the Beccas site Supabase tables.

Service key missingNEXT_PUBLIC_BECCASSITE_SUPABASE_URL missing
Add `BECCASSITE_SUPABASE_SERVICE_ROLE_KEY` in `.env` or Coolify and restart/redeploy the app. Public anon or publishable keys cannot write through Row Level Security.

Transfer Flow

From scraper database to Beccas site database.

1. Scrape and normalize

Zillow and Browser Use jobs create structured rental records with listings, buildings, landlords, contacts, amenities, images, and source metadata.

2. Store in the scraper database

The records first land in this control-center Supabase database. This is the review and quality-control layer.

3. Review and filter

Use the database cards to check descriptions, contacts, source links, landlords, buildings, and duplicate risk before pushing records to the public site.

4. Transfer approved records

The next implementation step is a controlled transfer action that maps these records into the Beccas site tables and upserts them safely.

Destination Setup

Connection status for the Beccas site project.

Supabase URLhttps://csyvhhimmldmmnhlgjsu.supabase.co
Server write keyConfigured
Anon keyConfigured
Publishable keyConfigured
Transfer writes require a server-side service role key. Public anon and publishable keys are shown for reference, but they are not enough for this import because Row Level Security blocks direct writes.

Recommended Mapping

How the current scraper records should move into the Beccas site tables.

Back to database

Landlords and property managers

Current table: landlords

Beccas site: landlord / manager records

  • Company or landlord name
  • Office phone and email
  • Website and office address
  • Verification status
  • Source site and original source ID

Buildings

Current table: buildings

Beccas site: building / property records

  • Building name and street address
  • Neighborhood, borough, city, state, zip
  • Latitude and longitude
  • Amenities and image URL
  • Primary landlord relationship

Listings

Current table: listings

Beccas site: rental listing records

  • Rent, beds, baths, sqft, availability
  • Full description
  • Amenities, images, virtual tour
  • Contact access and source URL
  • External listing ID for duplicate prevention

Rules Before Transfer

These rules protect the Beccas site from incomplete or duplicate records.

No duplicates

Use `source_site + external_listing_id` for listings, `source_site + external_building_id` for buildings, and `source_site + original_id` for landlords.

Description required

Listings should not be pushed to the live site unless a usable description is present.

Contact required when available

Listed-by, manager, phone, email, or office contact should be included wherever the source exposes it.

Keep raw source data

Preserve `raw_data` and source URLs so every published record can be traced back to its scrape source.