Migration · 11 min read

Leave Brilliant Directories
without losing your listings or SEO.

Brilliant Directories is powerful — and heavy. Many operators want faster iteration, clearer pricing, Google Sheets workflows, and 0% platform fees on listing revenue. This guide walks a practical migration to Row.so: export → Sheet → map fields → payments → domain → redirects.

What you should export first

Before canceling anything, pull a complete inventory of content and monetization settings.

  • Listings CSV/export with categories, tags, URLs, images, and custom fields
  • Member / claim accounts if you rely on them (plan how auth maps later)
  • Active paid plans, prices, and featured placement rules
  • Custom pages (About, Pricing, Submit) copy you want to keep
  • Analytics baselines and top landing URLs for redirect planning

Load listings into Google Sheets

Row.so treats Sheets as a first-class CMS. Paste or import your export into a clean Sheet with one row per listing and clear column headers (Name, URL, Category, Description, Logo, Featured, Price, etc.).

Normalize categories and tags before sync — messy taxonomies migrate as messy filters. Deduplicate URLs and fix empty required fields while data is still in the spreadsheet.

Create the Row.so directory and map columns

Create a new directory (AI prompt for structure if helpful, or empty). Connect Google Sheets, map columns to standard and custom fields, then run a manual sync. Preview cards and detail pages before inviting the public.

Rebuild monetization with native checkout

Connect Stripe, Lemon Squeezy, Polar, or PayPal. Recreate listing tiers (one-time, monthly, yearly) and featured homepage slots. Row.so takes 0% of listing revenue — payments go to your account.

  • Match previous price points first; optimize after traffic stabilizes
  • Enable auto-publish on payment where moderation allows
  • Test a full submit → pay → live listing path on a staging plan

Design, domain, and redirects

Customize home, category, and detail blocks to match your brand. Point DNS to Row.so and provision SSL. Add 301 redirects from old Brilliant URLs to new listing/category paths so SEO equity survives the cutover.

Cutover checklist

StepOwnerDone when
Full listing sync verifiedOpsSpot-check 20 random listings
Payments test chargeFounderListing publishes after pay
DNS + SSL liveOpsHTTPS on custom domain
301 map for top URLsSEOGSC shows no spike in 404s
Submit form + moderationEditorialQueue works for free/paid

FAQ

Yes. Export listings to CSV or Sheets, connect the Sheet to Row.so, map columns to fields, recreate paid plans, then point your domain and set redirects.

Not if you plan redirects. Export your top URLs, map them to new Row.so paths, and ship 301s at cutover. Keep titles and descriptions close on high-traffic pages.

No. Row.so takes 0% of listing revenue. You pay the platform subscription and keep listing fees in your Stripe, Lemon Squeezy, Polar, or PayPal account.

Small catalogs (under a few thousand rows) often move in a day. Larger datasets need more cleanup time in Sheets before sync — the platform cutover itself is usually hours, not weeks.

Put this guide into practice

Row.so is an AI directory website builder with paid listings on every plan — describe your niche or connect a Google Sheet and go live today.

Related use case →