Migration
rcore_housing can import existing properties from other housing resources, so you keep your players' homes when switching.
Two sources are supported out of the box:
vms_housing
qs-housing
The migration reads from the source resource's tables - it never deletes or alters them. Your old housing tables stay untouched, so you can roll back at any time.
Always back up your database before migrating. rcore_housing does not touch your old housing tables, but a fresh backup is the safe way to recover if anything goes wrong on your server.
▶️ Running a Migration
Run the matching command in your server console for the source you are migrating from:
migratehouses vms_housingmigratehouses qs_housingOnce it finishes, restart rcore_housing and your migrated properties will be live.
🟢 vms_housing
Migrated
Skipped (preserved in migration_source)
Properties
Furniture
Ownership
Bill history
Tenancy
Grass / designs
Sale / rent state
Gallery URLs
Zones
vms upgrades
Coords
IPL themes
Keys
Permissions
Utilities
Upgrades
🔵 qs-housing
Migrated
Skipped (preserved in migration_source)
Properties with full spatial data (coords, zones, entry, garage, exit, delivery)
Furniture, stash, outfit, decorateStash, vaultCodes
Ownership & tenancy (from player_houses.owner + rented)
Doorbell sound, assistant, wallart, vault, furniture capacity upgrades (no rcore equivalent)
Sale / rent prices (creditPrice, rentPrice)
sale_furnished / rent_furnished flags
Keyholders → guest accesses
Lights state (lights_on, lights_on_since)
Purchased upgrades (alarm, camera, motion sensor)
🗄️ Preserved Source Data
Skipped fields are stored on each migrated property in the migration_source column. This means:
You do not lose any data the source resource held.
Nothing is removed from your original
vms_housing/qs-housingdatabase tables.As
rcore_housingadds matching features in future updates, the preserved values can be applied back to these properties.
Last updated