WordPress Performance Optimization Consultant

Developer Brief: 220526

New Listing System Build + Data Migration


1. Project Overview
I am currently operating a business-critical directory website built on the Pixelgrade Listable theme (WordPress 6.2, PHP 7.4). The site contains 120+ company listings with text, images, videos, and map data.
The existing theme and plugins are outdated and cannot be upgraded safely.
The goal is to build a new, modern, stable listing system on a new WordPress installation (Cloudways staging environment), migrate all existing data, and introduce a paid subscription model for companies to be listed.

2. Objectives
• Build a new Listings system using modern, supported tools.
• Migrate all existing listing data (120+ companies) from Listable → new CPT.
• Preserve all media (images, videos).
• Implement a subscription-based payment system with variable pricing based on company size.
• Ensure the new system is compatible with Beaver Builder, PHP 8.0+, and WordPress 6.6+.
• Deliver a future proof, maintainable platform.

3. Technical Requirements
3.1 New WordPress Environment
• Build on Cloudways staging (client will provide access).
• Use PHP 8.0 or 8.1 (not 8.2+).
• Use WordPress 6.6.

3.2 Custom Post Type (CPT)
Create a new CPT called Listings using CPT UI.
Required taxonomies:
• Listing Category
• Region / Location
• Company Size (optional as taxonomy or ACF field)

3.3 Custom Fields (ACF Pro)
Use ACF Pro to create structured fields for each listing:
• Company Name
• Tagline
• Description
• Address (text)
• Latitude (number)
• Longitude (number)
• Company Size (select: Small / Medium / Large)
• Website URL
• Phone
• Email
• Logo (image)
• Gallery (repeater or gallery field)
• Video embed
• Social links (optional)

3.4 Front End Templates (Beaver Builder)
Create the following templates:
• Listing Card (archive view)
• Single Listing Page
• Listings Archive / Search Page
Templates must be fully editable in Beaver Builder.

3.5 Search & Filtering
Implement FacetWP (or JetSmartFilters) for:
• Keyword search
• Category filter
• Region filter
• Company size filter
• Map radius search (if required)

3.6 Maps Integration
Use Mapbox (preferred) or Google Maps.
Features required:
• Map on single listing
• Map on archive/search page
• Marker clustering
• Pull coordinates from ACF fields

3.7 Subscription / Payment System
Client requires paid listings with variable pricing based on company size.
Developer should implement ONE of the following:
Option A (preferred): Paid Memberships Pro
• Create subscription tiers (Small / Medium / Large company)
• Restrict “Submit Listing” to active subscribers
• Integrate Stripe for recurring payments
Option B: WooCommerce + WooCommerce Subscriptions
• Create subscription products
• Assign listing submission rights based on subscription
• Stripe + PayPal support
Developer to advise based on complexity and cost.

4. Data Migration Requirements
4.1 Export from Existing Site
Export all job_listing posts using WordPress Export Tool.
4.2 Field Mapping
Map Listable/PixTypes fields to new ACF fields.
Examples:
Old Field (Listable) New Field (ACF)
_job_location address
_geolocation_lat latitude
_geolocation_long longitude
_company_size company_size
_company_tagline tagline
Developer must confirm all field mappings.
4.3 Import
Use WP All Import + ACF Add on to import:
• Listings
• Categories
• Custom fields
• Media attachments
Media must be re attached automatically.
4.4 Verification
Developer must verify:
• All listings imported correctly
• All images and videos display
• Maps load correctly
• Filters work
• Subscription restrictions work

5. Additional Requirements
• Maintain SEO metadata (Yoast/RankMath) if present.
• Ensure fast performance (Cloudways caching).
• Ensure mobile responsiveness.
• Provide basic documentation for the client on how to:
o Add/edit listings
o Manage subscriptions
o Update templates

6. Deliverables
• Fully functioning new listing system
• All data migrated
• Subscription system operational
• Templates built in Beaver Builder
• Documentation for client
• Final site deployed to production (Cloudways)

7. Timeline & Budget
Client is cost sensitive.
Developer should propose:
• Estimated hours
• Fixed price option (if possible)
• Phased delivery plan

8. Access Provided
• Cloudways staging environment
• WordPress admin access
• Existing site export
• Mapbox API key
• Stripe account (for subscriptions)

Final Note for Developer
I am currently a one-person business.
The solution must be:
• Maintainable
• Lightweight
• Easy to update
• Future proof
• Not dependent on abandoned themes/plugins