Changes

From Gramps

Import from another genealogy program

9 bytes removed, 06:23, 1 November 2025
m
no edit summary
We recommend start by [[Start_with_Genealogy#Create_a_Family_Tree|creating a fresh, empty Tree]] and then importing... even if it is just as a test run.
Once the imported data is in Gramps, you can explore what needs cleaning. Maybe their export stored a duplicate of every place and source for the genealogy rather than building a hierarchy for each or even using the same identifiers. [[Gramps_{{Version manualman version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_3#Merging_records|Merging]] duplicate [[Merge_two_places|Places]] and Sources now will be much easier when there is a sole source for all the data. There are free Third-party Addon tools some users have created and shared to [[Addon:Import Merge Tool|make merging forked Trees easier]]. You can use this pruned Tree as a stepping stone to a cleaner import. It is always safer to import data already in Gramps format.
== Gramps to Gramps==
===== Known issues =====
You can set Confidence levels for your [[Gramps_Glossary#source|Sources]] in the [[Gramps_{{Version manualman version}}_Wiki_Manual_-_Entering_and_editing_data:_detailed_-_part_2#Citation_information|Citation Editor]]. These Confidence levels correspond to the [[Gramps_Glossary#gedcom|GEDCOM]] [http://wiki-en.genealogy.net/GEDCOM/QUAY-Tag QUAY] tag.
ending comment tag -->
# If two people are married, the "Family" screen in Gramps indicates in "Relationship Information" that their "Type" of relationship is "Unknown" rather than "Married." An example of the ramifications of this are that when printing a Narrated Website Report of John Doe who in reality was married to Jane Doe, and they had children, Jane Doe will not appear on the chart and the chart will not indicate that they were a married couple, though the marriage itself will be indicated as an "Event." To fix this issue, an adjustment must be made prior to importing the tmg2gramps generated XML file to Gramps. Under Gramps {{man menu|Edit-> Preferences-> Display}} the "[[Gramps_6.0_Wiki_Manual_-_Settings#Input_Options|Default family relationship]]" can be set to "Married" (or any of the others). Upon importing the database, all Family Relationship Information "Types" will then be set to "Married." Of course any Family unions that are not marriages will then need to be corrected, but you can set the default "Type" to be whatever the majority of your Families are.
# Related to the above issue, any "Disconnected individuals," married or otherwise, will remain disconnected. A TMG GEDCOM export and Gramps import designates a married couple as a "Family" whether or not they have any children — the "Disconnected individual" count is at zero — this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" — hence, the marriage is an "Event" and the unrelated spouse is considered a "Disconnected individual." Also, even if the family does have children, perhaps due to distant consanguinity, they will not appear as "Family." Fixing this gets complicated — you can go through the "Disconnected individual" list from the statistics of your database and manually create each missing "Family" that way, but that will still leave others that are potentially lost needles in a haystack. They can be found by [http://sourceforge.net/p/gramps/mailman/message/32487230/ running custom filters on the Person Filter Editor]. You will then be able to clearly see all the individuals who have marriages, but which tmg2gramps did not recognize as a "Family." You can then create each "Family" manually yourself.
# Any external media files may not be found. This can be resolved by correcting their path using the [[Gramps_{{Version manualman version}}_Wiki_Manual_-_Tools#Media_Manager |Gramps Media Manager]].
# Certain unique characters may not import properly into Gramps. Most accented characters did, but an "ñ" in TMG was imported to Gramps as "ń" — a TMG GEDCOM import into Gramps did not have this problem. It is easily fixed by editing the XML file directly and doing a find / replace.

Navigation menu