Sometimes a VendorHearth Pro installation needs to be moved to another WordPress website, transferred to a new domain, or reconfigured after major website changes.
Because VendorHearth connects several parts of WordPress, a successful migration involves more than simply moving the plugin files.
Before Making Major Changes #
Create a complete backup of your WordPress website before beginning.
Your backup should include:
- WordPress database
- WordPress files
- Vendor uploads
- VendorHearth data
- Website configuration
Do not remove the original installation until you have confirmed that the new installation is working correctly.
Moving to a New Website #
When migrating VendorHearth to another WordPress installation, use a migration method that transfers both the website files and database.
VendorHearth information is connected to your WordPress installation, so copying only the VendorHearth plugin folder is not a complete migration.
Moving Your License #
A VendorHearth Pro license is intended for one WordPress website.
When permanently moving the installation:
- Deactivate the VendorHearth license on the old site when possible.
- Complete the website migration.
- Install or verify VendorHearth on the new site.
- Enter your VendorHearth license key.
- Activate the license on the new site.
- Confirm the license status.
Do not publicly share your license key during the migration process.
Review System Readiness #
After the migration, open:
VendorHearth → System Readiness
Review all available checks.
Pay particular attention to:
- VendorHearth version
- Database/schema
- Portal pages
- User roles
- Role isolation
- Setup status
- Uploads
- Scheduled automation
- Payment configuration
Resolve significant warnings before reopening the system to vendors.
Verify Portal Pages #
Confirm that VendorHearth’s front-end pages still exist and are correctly assigned.
Important shortcodes include:
Vendor Registration[cmn_vendor_register]
Vendor Login[cmn_vendor_login]
Vendor Dashboard[cmn_vendor_dashboard]
Vendor Check-In[cmn_vendor_checkin]
Vendor Event Packet[cmn_event_packet]
Vendor Relations Portal[cmn_vendor_relations_portal]
Organizer Portal[cmn_organizer_portal]
Open the pages from the front end and confirm that they work.
Test User Roles #
A migration can sometimes expose permission or account problems.
Test VendorHearth using the appropriate roles, including:
- Administrator/Organizer
- Vendor Relations Manager
- Event Staff
- Vendor
Do not test everything only while logged in as a WordPress Administrator.
A page that works for an Administrator may still have an access problem for another role.
Review Square Configuration #
If your website domain changed, carefully review your Square configuration.
Confirm:
- Environment
- Application ID
- Location ID
- Access Token
- Webhook URL
- Webhook Signature Key
A domain change may require you to update the webhook destination configured in Square.
Test the payment workflow before reopening payments to vendors.
Test Email #
Send a VendorHearth test email after the migration.
Confirm that:
- The message is generated
- The From Name is correct
- The From Email is correct
- The message reaches the recipient
A server or hosting change can affect WordPress email delivery even when VendorHearth’s settings appear unchanged.
Review Scheduled Automation #
VendorHearth uses WordPress scheduled tasks for supported automation.
After moving the website, verify that WordPress cron is functioning properly.
This can affect features such as automated vendor reminders and other scheduled processes.
Check Uploaded Files #
Confirm that uploaded VendorHearth files are still accessible.
Review items such as:
- Vendor logos
- Product photos
- Event maps
- Vendor documents
- Other uploaded files
A migration that does not correctly transfer the WordPress uploads directory can leave database records pointing to files that are no longer available.
Review Vendor Spotlights #
If your site uses Vendor Spotlights, check existing WordPress posts after migration.
Verify:
- Draft spotlights
- Scheduled spotlights
- Published spotlights
- Featured images
- Scheduled publication times
Also verify your WordPress timezone.
Reconnect Social Sharing if Necessary #
If you use Jetpack or another WordPress social-sharing service, verify that the connection survived the migration.
A domain change may require the service or connected social accounts to be reauthorized.
Test an ordinary WordPress post before relying on automatic Vendor Spotlight sharing.
Test Important Vendor Workflows #
Before considering the migration complete, test the workflows your organization actually uses.
Consider checking:
- Vendor registration
- Vendor login
- Vendor Dashboard
- Event applications
- Payments
- Vendor Relations Portal
- Organizer Portal
- Event Packet
- Vendor Check-In
You do not necessarily need to recreate production records. Use appropriate test data when possible.
Reconfiguring Without Moving the Website #
These same checks are useful after major changes even if VendorHearth remains on the same domain.
For example, review VendorHearth after:
- Replacing portal pages
- Changing your WordPress theme
- Changing hosting providers
- Changing email providers
- Changing payment settings
- Changing important user-role configuration
Do Not Delete the Original Too Soon #
When moving VendorHearth to another website, keep the original installation available until you have confirmed that the migration was successful.
Verify the new installation before permanently removing the original site or its backups.
Final Migration Checklist #
Before reopening VendorHearth to vendors, confirm:
- License is active on the correct website
- System Readiness looks correct
- Portal pages work
- User roles work
- Vendor data is present
- Uploaded files are accessible
- Square is connected
- Webhook configuration is correct
- Test payment works
- Email works
- Scheduled automation works
- Vendor Spotlights work if used
- Social sharing works if used
- Event Operations tools work if needed
Once these checks are complete, your VendorHearth installation should be ready for normal use.
Next Step #
Continue to Troubleshooting for solutions to common VendorHearth problems involving access, applications, payments, email, automation, and other system features.
