# Moving Place Details from one Place to another

**URL:** <https://community.rootsmagic.com/t/moving-place-details-from-one-place-to-another/16276>\
**Category:** RootsMagic\
**Tags:** question, feature-request\
**Created:** [September 30, 2026, 5:05pm UTC](https://community.rootsmagic.com/t/moving-place-details-from-one-place-to-another/16276 "2026-09-30T17:05:30Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tstrickland](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.rootsmagic.com/tstrickland/32/7122_2.png) [@tstrickland](https://community.rootsmagic.com/u/tstrickland)\
**Post date:** [September 30, 2026, 5:05pm UTC](https://community.rootsmagic.com/t/moving-place-details-from-one-place-to-another/16276/1 "2026-09-30T17:05:30Z")

</div>

I have a few _Place Details_ (particularly cemetery names) that I put incorrectly into a specific _Place_. Now, I’d like to easily ‘move’ or ‘transfer’ those Place Details to their proper place.

_Example_: I incorrectly assigned **Zimmer Cemetery** to the location **Delwood, Pope, Illinois**. In reality, the cemetery was never in Delwood at all but simply a rural cemetery out in the county itself.

**Problem** : I’ve got about 22 ancestors with **Burial** _Fact Type_ records in this cemetery. I think my current fix is to open each of those 22 and delete the Delwood part of the Place Details, essentially creating a new Place Detail record in the Pope County Place. But then, all of the _Notes_, _Media_, _Tasks_ and _Webtags_ would then need to be manually copied into the new Zimmer Cemetery record.

**Request** : I’d like an easier method to simply mark (_maybe a checkbox_) a Place Detail to be moved, then have a pop-up selector of some sort to choose the new Place for that detail record. On the backend in the database, it would be a simple update to the _PlaceTable_.MasterID column for that Place Detail and an update to the affected Person records changing the Place of the Fact Type.

---

<div class="post-metadata">

**Author:** ![TomH](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.rootsmagic.com/tomh/32/30_2.png) [@TomH](https://community.rootsmagic.com/u/TomH)\
**Post date:** [September 30, 2026, 5:17pm UTC](https://community.rootsmagic.com/t/moving-place-details-from-one-place-to-another/16276/2 "2026-09-30T17:17:17Z")

</div>

That you know the database structure well enough to assert that it is simple to accomplish on the backend suggests that you are capable of doing your needed changes with your SQLite manager. So you don’t need this particular enhancement? How many others do and how many would it take to motivate the developers to put in the effort on it rather than on something else?

---

<div class="post-metadata">

**Author:** ![rzamor1](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.rootsmagic.com/rzamor1/32/8_2.png) [@rzamor1](https://community.rootsmagic.com/u/rzamor1)\
**Post date:** [September 30, 2026, 8:37pm UTC](https://community.rootsmagic.com/t/moving-place-details-from-one-place-to-another/16276/3 "2026-09-30T20:37:20Z")

</div>

Confirming request has been reported to development.

---

<div class="post-metadata">

**Author:** ![MadDog](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.rootsmagic.com/maddog/32/313_2.png) [@MadDog](https://community.rootsmagic.com/u/MadDog)\
**Post date:** [September 30, 2026, 8:39pm UTC](https://community.rootsmagic.com/t/moving-place-details-from-one-place-to-another/16276/4 "2026-09-30T20:39:53Z")

</div>

What happens when you do Places\>Tools Split Place ?  
That should work. Backup first 🙂

---

<div class="post-metadata">

**Author:** ![tstrickland](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.rootsmagic.com/tstrickland/32/7122_2.png) [@tstrickland](https://community.rootsmagic.com/u/tstrickland)\
**Post date:** [October 1, 2026, 2:37am UTC](https://community.rootsmagic.com/t/moving-place-details-from-one-place-to-another/16276/5 "2026-10-01T02:37:09Z")

</div>

> [@TomH](#):
>
> That you know the database structure well enough to assert that it is simple to accomplish on the backend suggests that you are capable of doing your needed changes with your SQLite manager. So you don’t need this particular enhancement? How many others do and how many would it take to motivate the developers to put in the effort on it rather than on something else?

@TomH thanks for the advice. But my intent is not necessarily to fix my personal problem at this moment. I’m well aware that fixes like this don’t happen overnight, and I could readily do it manually long before the code would ever be fixed/enhanced. My intent is to point out a functionality that would improve overall usefulness and simplicity for a problem I am sure others encounter. I am positive I’m not the first to add Place Details to then leave them orphaned by simply adding the detail to a different place. Or, that need to go back time after time and clean up those orphans… That’s kinda why a comment like mine is termed ‘feature-_request_’…

---

<div class="post-metadata">

**Author:** ![PatJ](https://avatars.discourse-cdn.com/v4/letter/p/54ee81/32.png) [@PatJ](https://community.rootsmagic.com/u/PatJ)\
**Post date:** [October 7, 2026, 12:17pm UTC](https://community.rootsmagic.com/t/moving-place-details-from-one-place-to-another/16276/6 "2026-10-07T12:17:31Z")

</div>

It’s a simple enough piece of SQL that would be a great enhancement to RM.
