Changes

{{languages|Import from another genealogy program}}{{man tip|Tips on importing from other genealogy programs}}There are several ways to import your family genealogy into Gramps from another program. The best option depends on what program you want to provide the information. But all import processes start with having a Gramps database (called a [[Genealogy_Glossary#family_tree|Family Tree]]) open and waiting to receive your family information. You could import directly into an existing Gramps Tree that already contains the fruits of many hours of research and organization. But since all Genealogy programs make different assumptions about how to organized and transfer data, that would not be a good practice. Their exported data might be a chaotic mess that mangles your nice, clean genealogy in Gramps.  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 manual}}_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== This is the easy one. The simplest and safest method to move all your information from one Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first Gramps. (If your Family Trees menu does not have an Import menu option, then you probably need to [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Starting_a_new_Family_Tree|create a new, blank Tree]]; or, [[Gramps_{{man version}}_Wiki_Manual_-_Manage_Family_Trees#Opening_a_Family_Tree|load an existing Tree]]. There must be a destination available before importing is possible.) Follow the instructions, choosing {{man label|Gramps Package}} for the format to save. And do not forget to disable privacy &amp; living person filters. Copy the file created by Gramps to the destination computer. Then in Gramps on that computer, choose {{man menu|Family Trees -> Import}} and select the transferred file.=== What's not included? === {{Template:Backup Omissions}} == Standard GEDCOM as transfer tool==  Most programs storing family history data can export and import [[GEDCOM]] (<code>.ged</code>) files. But, because the 1996 vintage GEDCOM data file specification remained in "''Draft''" status from Oct.1999 to Nov.2019, every genealogy tool has had to take liberties to shoehorn their data into something that has been long outgrown. (See the sections below to see a list of idiosyncrasies reported in different Genealogy software tools.) You would be unlikely to find any tool generating a 100&#37; compliant and ''standard'' GEDCOM format. {{man warn|Gramps does not currently (November 2023) import [[GEDCOM_7_support|GEDCOM 7]]|Revision [https://gedcom.io/specifications/FamilySearchGEDCOMv7.html 7.0.13 published on 4 August 2023]. <br />Although first announced May 2021, the [https://www.familysearch.org/en/GEDCOM/implementation-progress GEDCOM 7 implementation progress] list is still very thinly populated. Due to the lack of broad support, the new version cannot be recommended as a transfer tool.}}{{man tip|1=Selecting the best GEDCOM option|2=Given the choice, export options listed as "GEDCOM 5.5 Standard" tend to be the most broadly conformant type of GEDCOM.}}Due to these idiosyncrasies and dialects of GEDCOM, you should always [[CategoryHow_to_make_a_backup|make a backup]] before importing any GEDCOM file. <ol><li>Check the documentation for the originating program to learn how to create a GEDCOM file with all your data. </li><li>In Gramps, create a blank Tree database to accept the imported data.</li><ol style="list-style-type:lower-alpha"><li>Open the Family Tree Manager by choosing the '''Family Trees''' {{icon|ance}} icon in the toolbar, or in the menu {{man menu|Family Trees -> Manage Family Tree}}</li><li>Click the {{man button|New}} button to create a new family tree</li><li>Select the new family tree and click the {{man button|Rename}} button to enter a new name</li><li>click on the {{man button|Load Family Tree}} button to open.</li></ol><li>Now that a blank family tree database is ready, select {{man menu|Family Trees -> Import}} from the menu.</li><li>Start the import</li><ol style="list-style-type:How lower-alpha"><li>Use the File Selector to locate the GEDCOM file created by your originating program</li><li>select the GEDCOM file</li><li>click the {{man button|Import}} button</li></ol></ol> {{man warn| Verify the data |Check your data carefully once imported into Gramps. There are many things GEDCOM does not support that may be lost during transfer. In addition, many commercial programs do not create standard GEDCOM files. While effort is given to import as many files while preserving as much data as possible, Gramps aims to support the GEDCOM 5.5.1 standard.}} Ensure that your media files are transferred too, and found by Gramps. In the menu {{man menu|Tools -> Utilities}}, you will find the {{man label|Media Manager}}. If needed, this allows you to change the path of your media objects to the new path. == Spreadsheet import == Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your data for importing into Gramps.  The CSV import option currently doesn't allow import of all Gramps data.  For example, it doesn't import all of a person's events and notes. It does import/export birth, death, and marriage events---and notes for those events, people, and marriages.  For more details on this format see [[Gramps 5.1 Wiki Manual - Manage Family Trees: CSV Import and Export]]. == Addon == [[Addon:GEDCOM Extensions]] should be able to handle unofficial GEDCOM extensions. == Import instructions for different programs == === Ancestrologie === Ancestrologie seems to produce non-standard GEDCOM for some kinds of data. In general such problems should be repaired prior to importing into Gramps.  ==== Programs for fixing some of the known problems ====Download and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the comments. ; [http://pub.jgsack.net/g_scripts/fix_Ances_repo.py.gz fix_Ances_repo.py.gz] : Script to fix non-standard gedcom address data REPO citation within a SOUR record. It replaces the (crash-causing) address data with a REPO reference and adds a REPO record containing gedcom-standard address elements. ; [http://pub.jgsack.net/g_scripts/fix_Ances_map.py.gz fix_Ances_map.py.gz] : Script to fix non-standard LATI/LONG PLAC data that should be in a MAP structure per the 5.5.1 spec. ; [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] : Script to fix various non-standard GEDCOM usage or GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like: 2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111 The data (in this case 75111) may be absent or extend to CONT lines.The non-standard elements converted to APPX notes include: ; _ANCES_CLE_FIXE : Special internal reference : "Who they are ?"; _ANCES_ORDRE : Considered non-critical, events classification ; _ANCES_XACTE : Non-critical (certificat found = 1); _ANCES_XINSEE : INSEE geographical code (evidently ''simplified 5-digit''); EVEN F : Invalid EVENTS_RECORDED format in a SOUR record; EVEN I: (Same); LIEU : A subdivision of place, is not our place but a division; XTYPE : These seem to be OBJE subordinates; XIDEN : Considered non-critical, media object used for primary media (photo); XMODE : (file is not present at the FILE address) In addition, one other change, replaces a non-standard "FILA" item to the GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.  1 FILA Enfant légitime  becomes  1 FACT Enfant légitime 2 TYPE FILA '''Users are invited to correct/clarify the above information or notify us of additional problems with non standard GEDCOM or GEDCOM extensions.''' '''Please also feel free to provide feedback on broken scripts or incorrect ''fixes''''' -----=== Ancestry.com === Older Ancestry.com GEDCOM export files had a relationship compatibility faults in their GEDCOM format and, beginning with the 3.0 release, Gramps handles this seamlessly. In a test done in 2016, Ancestry.com had corrected that fault in their GEDCOM format and their newer files are also recognized for proper import into Gramps,  But some GEDCOM idiosyncracies remain. These notes are based on work importing a gedcom with 2000 individuals and 60000 lines of information into Gramps V4.2.5.==== Records not imported ====There were around 8000 lines that were reported as "not imported". They were the following categories:* '''_APID''' records comprise the majority of messages - they are a record type specific to Ancestry internal cross-referencing identifiers and probably meaningless anywhere else. * many '''NOTES''' records are listed as ignored because they are ''empty'' - checking the gedcom shows this to be correct.* a very small number show as "''Tag recognised but not supported''". This coincided with duplicated source entries ''SOUR'' linked to the same source object but with ''_APID'' subrecords having different values.Those three import failure types do not create any problem for use with Gramps, and can be ignored, however you should make a point of carefully scanning the import report to ensure there were no failures for other reasons. The GEDCOM layout used by Ancestry for each item seems to not be consistent, and might change depending on the time at which the initial entry was made into the Ancestry.com tree.==== Scan for Errors====Use the {{man menu|Tools-> Family Tree Repair->Check and repair Database}}. Any media objects in the Ancestry.com tree will not be imported, but each will have a caption and url that will not generally work without being able to login to an active Ancestry.com account. Depending on your intended actions with regard to media, you can keep these or select for Gramps to ''remove missing objects''. There were 5 events that in the source gedcom were given as ''1 BIRT Y'' with no subordinate records. Gramps apparently rejected these as "''events were referenced, but not found''". They are valid according to the GEDCOM specification, but quite redundant since all they say is that the person was born. ==== Source objects ====The empty source objects are not deleted, but are replaced by entries with a note and the title "unknown".You can click on ''Sources'' in the navigator, select one and view the associated ''Notes'' tab, which should just show the associated warning inserted by Gramps Check and Repair. Provided there is nothing useful in the Notes, you can select all these "Unknown", ''edit->remove''.==== Notes ====Select ''Notes'' under the navigator. For each individual, family or source object a note will be created listing all the gedcom problems for that object, starting with the text "Records not imported into ..." . Scroll down to these lines (ensure pages are sorted by ''Preview''. Alternatively, create a suitable filter: enter "^Records not imported into" into the text box (without the quotes), enable "Use regular expressions" and click Find. You may wish to select and remove all of these, provided you have established there are no significant errors in the import. The blank '''NOTES''' and the Ancestry-specific '''_APID''' records are of no use here, and they ''cannot be re-exported'' for reading back into an Ancestry tree.==== Dates ====Ancestry seems to allow some date options that aren't consistent with the restrictions of GEDCOM standard.Their export does not always convert these to the [http://wiki-en.genealogy.net/GEDCOM/DATE-Tag valid GEDCOM date format]. There seems to be no automated method to fix these. These are identified in a default configuration by displaying the bad dates in bold in the display area. Gramps will fix some if you simply open an event and then save; others need manually editing. A more efficient way to check is use {{man menu|Tools->Utilities->Verify the Data}} and enable "Identify Invalid Dates" ==== Final cleanup of Ancestry's empty export records ====A search for unused objects ({{man menu|Tools->Family Tree Repair->Remove unused objects}}) can identify and delete any remaining problems. ==== additional Ancestry notes ====[https://progeny.zendesk.com/hc/en-us/articles/215558727-How-to-export-your-data-out-of-Ancestry-com How To: export your data out of Ancestry.com] [https://www.reuniontalk.com/forum/using-software-hardware-with-reunion/9126-ancestry-apid-tags-and-reunion More about Ancestry.com's APID record identifiers] [Gramps-devel] [[Contact#Mailing_lists|Mailing list]] discussion of advanced handling of APIDs:* [https://sourceforge.net/p/gramps/mailman/message/34938458/ Gramps and Ancestry hints - a proof of concept] See Bug Report {{bug|899}}: to learn about '''grampify.pl''', an addon tool (superseded by Gramps version 3) for fixing broken (Relationship lost) GEDCOM generated by Ancestry.com----- === Evidentia ===If you do source and evidence-based genealogy research, you might use this (commercial) program to help you follow the [https://bcgcertification.org/ethics-standards/ Genealogical Proof Standard] (GPS). If so, you need to understand which information [Categoryhttp:Developers//evidentiasoftware.com/evidentia-step-by-step Evidentia] will and will NOT export and import via GEDCOM. ==== Generaltips ====When you are entering information into Evidentia (about people, places, sources, etc.), be sure that it is typed EXACTLY as you entered it into Gramps. This makes it more likely that it will transfer successfully from one program to another. ==== People ========= Import into Evidentia as subjects =====First, export individuals from your Gramps database into a GEDCOM file, either your entire database, or just those people you are currently researching. Next, import those people into Evidentia as what the program calls "Subjects" under the "List Manager" option.  ===== What Evidentia imports and exports =====Evidentia will only save enough data so that you can clearly identify which person you are researching. Evidentia can import and export these basic GEDCOM fields about a person: ; @I0000@ INDI : Person's ID number, called a "Reference number" in Evidentia; NAME Lakshmi /Wolowitz/ : Full name; GIVN Lakshmi : Given name); SURN Wolowitz : Surname; SEX F : Gender; BIRT : Birth year ==== Events and facts ====As mentioned above, Evidentia can import the Event (sometimes called Fact) of a person's birth. However, that is the ONLY event that can be imported in the current version. ===== Manually add facts into Evidentia =====The main use for Evidentia is to properly cite and "prove" facts (or events) about people. So, you are required to enter those facts into Evidentia as a "Claim Type", attached to a specific Subject (person), and supported by source citations. ===== Export some types of facts to Gramps =====Evidentia has most of the main types of claims you'd expect (birth, residence, etc.) and will export them to the usual GEDCOM fields. If a Claim Type doesn't exist in the original list, though you have to add it. It is unclear if an added Type will export to GEDCOM.  ==== Sources and Citations ========= Manually add to Evidentia first =====Enter your sources and citations into Evidentia first. Only after you've finished creating your proofs in Evidentia should you then import your source citations into Gramps. There are two reasons to follow this workflow:* First, Evidentia currently has no way to import your sources or citations, so entering here first means you don't have to enter them twice.  * Second, Evidentia makes it easier to use the 170 source citation templates from Elizabeth Shown Mills, so your sources and citations will be properly formatted! ===== Match your source title and source abbreviation =====When a source is exported from Evidentia, it uses the "Source Title" for both the title (TITL) and the abbreviation (ABBR) fields in GEDCOM. So, if you've already created Sources in Gramps, use the same text in both of these fields, as well as in both programs. ===== Complete publication information exported =====Evidentia exports a full and complete reference listing (PUBL) for each source, which includes the title. So you might want to exclude the title of sources from the complete individual report in Gramps to avoid duplication. ===== Citation title only used in Evidentia =====Citation titles are only used within the Evidentia program, and don't effect Gramps. So, choose whatever pattern you like for naming them. ==== Claims and proof ========= Default GEDCOM export =====When you export a "Subject" into a GEDCOM file, Evidentia's default export will automatically include that person's: * Individual information: id, name, gender* Claim type: facts, events, or attributes* Source information: title, abbreviation, and full publication info (PUBL)* Full citation (PAGE) If you entered a date (DATE) or place (PLAC) for a particular claim (event/fact), that will also be exported, so be sure to type the place name in precisely to avoid creating duplicates in Gramps. ===== Evidentia-specific GEDCOM export =====Evidentia's GEDCOM export does not include the full Proof Report (although you could save that report as a PDF and add manually add it to your media in Gramps). If you do use Evidentia's recommended export settings, the claim analysis will be added as a note to the citation, and the proof conclusion will be added as a note to the event/fact. For example: * Citation Note with the Claim Analysis: "The 'Citation Title 1' asserts that Lakshmi Wolowitz was 30 years old when this census was taken in 1840. The age given in the 1840 census suggests that Lakshmi was born about 1810. However, the accuracy of census data varies widely."* Event Note with Proof Conclusion: "Until given stronger evidence of Lakshmi's birth date, it can only tentatively be concluded that she was born in 1810." === Family Tree Maker === GEDCOM is currently the only option for copying your data out of Family Tree Maker and into Gramps. Follow the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]].{{man tip|1=Recommended Reading|2=When Ancestry startled Family Tree Maker (FTM) proponent Keith Riggle by announcing it's retirement, he posted a frank critique of exchanging data between FTM & Gramps v4.0 in [https://genealogytools.com/replacing-family-tree-maker-part-8-importing-your-ftm-tree-into-gramps-4/ Family Tree Software Alternatives, part 8] article of the [https://genealogytools.com/ Genealogy Tools] blog.<br>''extensively revised for Gramps 5.0 on 8 Aug 2018''}}==== If you do not have access to Family Tree Maker ====(Tested with FTW file created by Family Tree Maker 2006)* Download and install the free MyHeritage Family Tree Builder:http://www.myheritage.com/family-tree-builder* Create a new account (with bogus data)* Disable any syncing features when asked* Create new Project: File > New Project...* File > Import GEDCOM... > Browse > Select FTW file* File > Export GEDCOM... ==== Family Tree Maker 2005 ==== Select File -> Export File -> Entire File...In file dialog, enter a filename and select "GEDCOM(*.GED)" from the "Save as type" dropdown.In the "Export to GEDCOM" dialog, set the following:* Destination: FTM* GEDCOM: Version 5.5* Character set: ANSI (Gramps will convert to UTF-8 upon import)* Deselect "Indent records"* Select "Abbreviate tags" Media objects must be imported manually. It's a painfully laborious process. Here's a trick that might help ease the pain: Bring up the "Scrapbook" view on any family member. Press F2, which lists all individuals. By double-clicking on an entry, it will take you to that individual's scrapbook page. Pressing F2 again will bring up the list at the point where you left off. {{man note|Description or value associated to event on place field|Gramps made an exception for Family Tree Maker, which violates the GEDCOM spec by using the PLAC field to store the description or value associated with the event. Unfortunately, Gramps cannot fix all errors and tries to do the best for properly importing user data.}} ==== Known issues or custom extensions ==== # Blank lines# Issues on date string# PHON in INDI records# PLAC for general data# The source quality is coded as a NOTE rather as QUAY# Marriage start status# Double dates use the first date rather than the second ==== Programs for fixing some of the known problems ==== ; [http://west-penwith.org.uk/misc/FTWGEDfx.htm FTWGEDfx] : An open source freeware to fix the GEDCOM output from Family Tree Maker Version 7.0 for Windows. ====Experimental way==== [[Import_from_another_program#The_Master_Genealogist_.28TMG.29 |The Master Genealogist]] provides a way (via [http://www.whollygenes.com/Merchant2/merchant.mvc?Screen=PROD&Product_Code=GENBRDG-DL GenBridge]) to import FTM native database. [[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [[Gramps XML]] file, which could preserve more data. === Geneweb === Gramps can directly import from Geneweb. Choose {{man menu|Family Trees -> Import}}, select your Geneweb database and choose {{man button|Open}}. === GenoPro === ==== Gedcom ==== GenoPro can generate custom (invalid) GEDCOM [http://sourceforge.net/mailarchive/message.php?msg_id=27539893] but also better one [http://sourceforge.net/mailarchive/message.php?msg_id=27547464]. ==== GenoPro to Gramps ==== Experimental converter (.gno to .gramps) on {{bug|2757}}. === Heredis === ;Modifications of GEDCOM from Heredis to import in Gramps ''With editor (like gedit or note++) find and replace '''« > »''':''   ;1. Non standard tags of Heredis '''Like: ''' _CLS, _FIL LEGITIMATE_CHILD, _UST MARRIED, SIGN...  1 _FIL LEGITIMATE_CHILD > suppress all lines 1 _UST MARRIED > suppress all lines 1 RESN privacy > suppress all lines NOTE * > TITL * for medias titles ''(A star was added in all media notes before Heredis export)  ;2. Assign value Y to following to tags 1 BIRT > 1 BIRT Y 1 DEAT > 1 DEAT Y 1 MARR > 1 MARR Y 1 MARC > 1 MARC Y 1 DIV > 1 DIV Y 1 CHR > 1 CHR Y 1 ... > 1 ... Y  ;3. Sources and Repositories  1 QUAY "> suppress cr and values in quotes for all lines ''(quality appears at the end of publication value)'' '''3 MEDI > 1 MEDI or 1 PUBL''' _ARCH > AUTH  ;4. Change levels in Associations 2 ASSO @398195I@ > 1 ASSO@398195I@ 3 TYPE INDI > suppress all lines 3 RELA > 2 RELA  3 TITL > 2 TITL  3 NOTE XXX > 2 NOTE XXX If a note is associated  ;5. Équivalents of disks drives when loaded Linux Gramps FILE X:\YYY\Photos\ > FILE /media/ZZ/YYY/Photos/ FILE X:\YYY\Photosjrg\ > FILE /media/ZZ/YYY/Photosjrg/  ;6. For people's tags located in Events instead of Attributes Description Type Profession > Occupation Titre > Nobility title No (signe) > null YES (end of line) > null There would be a way to assign some fields in attributes instead of events. It's a mix up. By ''Ifs, Oct 25 2011'' ====Known issues====  According to "''Ancestris''" wiki, GEDCOM generated by Heredis may : # Add some empty tag - need to add Y on most event DEAT, MARR, MARC, DIV.# Not properly manage dates (calendars)# Generate custom tags without _ : WWW, EMAIL, HEAL, etc.# Not properly manage sources and repositories There are some alternatives to GEDCOM generated by Heredis : * Heredis format to GEDCOM : [http://sourceforge.net/projects/hr2ged/ project on sourceforge].* A python library to "read-only" Heredis file : [http://sourceforge.net/projects/hrlib project on sourceforge].* Heredis format to Database : [http://loic.fejoz.free.fr/hr2db/ project (in french)].* Heredis format to SQLite : [http://www.chroniquesdantan.com/retour-dexperience/dheredis-a-excel-pas-a-pas experimental way between two proprietary formats via SQLite]! === Legacy === According to "''Ancestris''" wiki, GEDCOM generated by Legacy may : # introduce a management issue on ADDR tag : need to add a RESI tag as parent tag/level.# ignore SOURCE_REPOSITORY_CITATION.# modify MEDI tag design, which can be used into CALN. [https://web.archive.org/web/20220921214605/http://support.legacyfamilytree.com/article/AA-00520/14/Tips-and-How-Tos/GEDCOM-Files-Custom-tags-in-Legacy.html Legacy Family Tree version 7 has an extensive list of custom tags] in their GEDCOM writing. === MinSläkt === MinSläkt (MyFamily) is a Swedish genealogy program for Windows by [http://www.dannbergsdata.se/ Dannbergs Data]. <!-- the following section is commented out (hidden) until the importing GEDcom Confidence section is written ==== GEDCOM ==== Instructions for exporting GEDcom from MinSläkt  ===== Known issues ===== You can set Confidence levels for your [[Gramps_Glossary#source|Sources]] in the [[Gramps_{{Version manual}}_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 --> === Pro-Gen === PRO-GEN is a Windows compatible genealogical program originally written by Johan Mulderij and Dinant Scholte in't Hoff in 1989. For more information, see their [https://www.pro-gen.nl www.pro-gen.nl] website.  Using GEDCOM to export data from PRO-GEN dropped a significant amount of data. Therefore an Importer plugin was created that reads the native PRO-GEN. The plugin is included in the standard Gramps distribution. To import the data, Gramps needs to be able to locate the Pro-Gen directory tree. This path depends on the PRO-GEN installation and setup. The version 3 of PRO-GEN might create a ~/pg30 folder. If you are running Gramps on a Windows PC and have a copy Pro-Gen on that same computer, then no export or copying to another device is necessary before starting the import.  Another possibility is to ZIP everything on your Windows computer and unZIP it on your Linux or macOS PC in, say that ~/pg30 folder.  In the following steps, we will assume that the Pro-Gen files are at ~/pg30 Import the data:* start Gramps* From the {{man menu|Family Trees}} menu, select "Manage Family Trees..."* use the "New" button to create a new family tree database* Give the Tree a name (like "PRO-GEN imported Tree") and select that new database* click the "Load Family Tree" button to open the blank tree database* go to menu {{man menu|Family Trees -> Import}}* in the file Selection dialog, go to the ~/pg30/nl/data directory* select the .DEF of your Pro-Gen database* in the drop-down selection box you have to select "Pro-Gen" (it is not automatically selected)* click "Import"* wait as the data processes... To see counts of the records that were imported, use the {{man menu|Reports -> Text Reports -> Database Summary Report}} (Be sure to select the optional "Open with default viewer" checkbox or the report will complete silently and not be displayed.)

== GRAMPS RootsMagic is a Windows program that offers features to GRAMPS==synchronize data with Ancestry and FamilySearch, and show hints from these sites and Find-My-Past and My Heritage. It also runs quite well in Linux, with Wine.

This is the easy oneImport of GEDCOM files created by Gramps works without problems, and fast, except when you split surnames into multiple parts. The simplest and safest method to move all your information from one GRAMPS program to another on a different computer is to choose ''They will then be imported as parts separated by comma' File -> Export ''' from the first GRAMPS. Follow the instructionss, choosing {{man label|GRAMPS Package}} for and the format same will happen to saveprefixes, if they exist.

Copy the file created by GRAMPS to the destination computer. Then in its GRAMPSExported GEDCOM files are quite clean, choose ''' File -> Import ''' and select when you clear the transferred file.checkmarks for

Most programs for family history can export and import [[GEDCOM]] (.ged) fileswhich are available in the bottom left of the Gedcom Export Options screen.

# Check the documentation for your program to learn how to create a GEDCOM file with all your data. #* If you have a choice, GEDCOM 5.5 Standard The export of tasks is usually the safest type of GEDCOM.# In GRAMPS, choose ''' File -> Import '''# Locate the GEDCOM file created disabled by your programdefault, and choose {{man button|Open}}untested.

{{man warn| Check RootsMagic has full support for source/citation templates, inspired by Evidence Explained and similar sources. The Results |Check your data carefully once imported into GRAMPS. There information entered for those is stored in specialized attributes, which are many things GEDCOM does not support that may be lost during transferexported when the Extra details checkmark is cleared. In additionAnd when you use templates, many commercial programs do not create standard GEDCOM files. GRAMPS does its best to do you may find formatted citation sentences in the right thing with non-standard GEDCOM filesfields, but it can't possibly cope with everythinglike TITL and PAGE. These fields may also include HTML markup for italic and bold.}}

Take special attention RootsMagic 9 has a quirk that your media files are transferred too, and found by GRAMPSduplicates PAGE information into a NAME tag that should not be exported in the citation. In the menu ''' Tools -> Utilities '''This can cause lots of import warnings in Gramps, you will find the {{man label|Media Manager}}, with which you can change the path of your media objects to the new path if neededbe discarded.

For many people, using GEDCOM will lose too much information, most notably "Witness" information.  If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps]. Though it is a little more involved, the results are often worth the extra effort. For those who don't find the guidance in tmg2gramps own [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file to be enough, the step by step instructions [[Import_from_another_genealogy_program#Running tmg2gramps | below]] are a bit more user friendly for the novice user, particularly when setting up the necessary MySQL database. You can also download tmg2gramps [[Media:Tmg2gramps.tar.gz|here]]. tmg2gramps was designed to, though '''"...convert what it can to a Gramps V2.2.6 xml file. This file can then be imported into Gramps, V2.2.6 or higher."''' Since then, Gramps has evolved. Testing has been done using tmg2gramps to convert a TMG v6 database and importing it to both Gramps 2.2.10 and 4.0.4. Despite being designed for Gramps 2.2.6, tmg2gramps works (at least in the test case) even better when importing to Gramps 4.0.4. Gramps 3.4.8 and 4.0.4 are more or less the same at the XML import level, so this should apply to importing to Gramps 3.4.8 as well. {{man note|Note|The official version of tmg2gramps does not work with well with TMG v8 databases, because of changed relation types. This can be corrected with a modified tmg2gramps.pl file, which can be downloaded [[Media:Tmg2gramps-v8.gz|here]] or [https://github.com/sam-m888/tmg2gramps/tree/master/tmg2gramps-v8 here]. To apply this upgrade, you must first unpack the official download, and then overwrite the tmg2gramps.pl file with the version above.}} ===== Data tmg2gramps successfully converts ===== Some data that tmg2gramps successfully converted from a TMG v6 database which a GEDCOM 5.5 export from TMG did not, are as follows: *"Witness" information. *"Places" data from TMG are put into the correct, corresponding fields in Gramps. GEDCOM puts all TMG "Places" data into Gramps' single "Place Name" field. *Various "notes" from TMG do not transfer over at all via GEDCOM and those that do are categorized simply as "General." tmg2gramps appears to transfer over most (if not all) the notes and breaks them into categories. The categories are not always entirely appropriate (see below regarding citations and "Source text" notes), but the information is aimed at advanced usersthere and can be corrected in Gramps. *tmg2gramps appears to transfer all TMG Tags to Gramps as "Events." (However, see [[Import_from_another_genealogy_program#Known_issues_3 |below]] for some minor issues related to this.) GEDCOM transfers some, but not nearly all TMG Tags.

Here are some known issues that have occurred when using tmg2gramps to convert a TMG v6 database and importing it to Gramps v4.0.4-1: # Events in Gramps from unique [http://tmg.reigelridge.com/Tags.htm TMG tags] sometimes have minor issues. For example a TMG Birthilleg tag will definitely show up in Gramps as an "Event" with all of the correct information, but it will not be designated as a birth &mdash; so if you look at that person in a chart in Gramps, the birth field will remain empty until you change the Birthilleg "Event" to a Birth "Event" (and you can mark the birth as illegitimate in a note).# Any Godparent relationships won't convert at all. However, each one of them is displayed by tmg2gramps once it is finished, so they can easily be copied and pasted to a document for manually entering into Gramps later.# Any information regarding a citation is put into a "Source text" note in Gramps. The "Source text" is associated with both the "Source" itself and the specific "Citation," so all the information is there, even if the description being a "Source text" is not accurate. Also, this leaves the "Volume/Page" field in the "Citation" blank, even if there is a volume or page number in the "Source text." An adequate but not perfect fix for this is to edit the XML file directly (''after'' exporting it from Gramps) and do a find / replace of type="Source text" with type="Citation" &mdash; this turns each "Source text" note into a "Citation" note. The "Volume/Page" field remains blank, but presumably that information is now in the "Citation" note which is not entirely inappropriate.# 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 "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 &mdash; the "Disconnected individual" count is at zero &mdash; this is the Gramps recommended practice. For couples without any children, a tmg2gramps import will not recognize the relationship as a "Family" &mdash; 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 &mdash; 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 manual}}_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 "ń" &mdash; 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. ===== Preparing to run tmg2gramps ===== Successfully running tmg2gramps for the first time can be a bit daunting for non-programmers, but is still of course quite feasible. The following instructions were written based on using a TMG v6 database and running tmg2gramps on Linux Ubuntu 14.04. ====== Copy your TMG projects folder ======Before beginning, copy your entire TMG '<code>projects</code>' folder to your linux home folder. It is also a good a idea to keep a backup copy of your TMG '<code>projects</code>' folder for posterity, just in case you may someday need it. On Windows XP, the TMG '<code>projects</code>' folder is located here: <code>C:\Program Files\The Master Genealogist\projects</code> ====== Rename your copied TMG projects folder ======Once you've copied it, rename the copied '<code>projects</code>' folder to '<code>tmgdata</code>' ====== Convert TMG filenames to lowercase ======Now, in order to run tmg2gramps properly on linux, it is necessary to make sure the contents of '<code>tmgdata</code>' is all lowercase, including extensions. The easiest way to achieve this is to open your linux terminal and navigate to the '<code>tmgdata</code>' directory. Once there, simply type this at the command prompt: <code>$ rename 'y/A-Z/a-z/' *</code> ====== Prepare MySQL ======Some users may already have MySQL installed or may not know if they do or not. Try installing it by typing the below in the a linux terminal: <code>$ sudo apt-get install mysql-server</code> That will either install MySQL, or if it is already installed, it won't cause any harm. The same is true with the xBase DBI connectors, some users may already have them installed. The following command in terminal will install it for those who don't, while those who already do have it will not be affected: <code>$ sudo apt-get install libdbd-xbase-perl</code> Now, enter MySQL. If you previously installed MySQL you may or may not need a password to get into it. If no password is required, users should be able to login to MySQL just by typing this at the command prompt: <code>$ mysql -u root</code> If that works, users can skip this next step. But if a password is required, this should be typed in terminal instead: <code>$ mysql -u root -p</code> You will now be in MySQL. It is possible that users attempting to use tmg2gramps before may have already created a MySQL database for this purpose. To check and see which databases are there, type this at the prompt: <code>mysql> show databases;</code> That will display which databases (if any) already exist. If there is no database for running tmg2gramps, one can easily be created (for our purposes, called <code>tmg_gramps</code>) by typing this at the mysql prompt: <code>mysql> create database tmg_gramps;</code> Now, make sure that you can connect to the database with the appropriate password and privileges by typing: <code>mysql> grant all privileges on tmg_gramps.* to grampsuser@localhost identified by 'grampspass';</code> You can now exit MySQL: <code>mysql> exit</code> === Family Tree Maker === Preparation for the tmg2gramps script ======...and prepare to run tmg2gramps. Make sure that you know the original name of your TMG project that you are going to convert. To check this, in terminal, navigate to the '<code>tmgdata</code>' directory which should be in your home folder. Once there, simply type this at the terminal to see a list of the files inside: <code>$ ls -l</code> This will display all the files listed in the folder. The name of your TMG project (or projects if you have more than one) will be the name of the file that precedes the underscores. For example, if your project (or one of your projects) is called 'smith,' you will see files such as: <pre>smith__.accsmith__.pjcsmith_$.cdx....</pre> ...etc. Make note of the name of the project that you would like to convert. The files and extensions should all already be lower case because of one of the early steps above. And lastly, '''before running tmg2gramps, it is necessary to make sure that you have the proper permissions set to execute it'''. In terminal, navigate to the directory where you unpacked tmg2gramps and type the following: <code>$ chmod +x tmg2gramps.pl</code> Now, it is finally time to run tmg2gramps and convert your data. ===== Running tmg2gramps ===== When running tmg2gramps, the example below makes the following assumptions: * Name of TMG project: '''''<code>smith</code>'''''* Home directory: /home/'''''<code>asmith</code>''''' Keeping that in mind, once again navigate to the folder where you unpacked tmg2gramps. Type the following in terminal, substituting the '''''bold and italicized''''' terms below with the terms appropriate for your specific circumstances (based on the above):  $ ./tmg2gramps.pl /home/'''''asmith'''''/tmgdata '''''smith''''' converted_'''''smith'''''_tmgdata.xml tmg_gramps grampsuser grampspass You should now be able to watch tmg2gramps running in terminal. The conversion process can create errors and it is advised to copy and save them. There can be all kinds of reasons for errors (for example, a Godparent relationship) and if you've saved them to a text file you can correct the imported data afterwards. When tmg2gramps has finished running, converted_'''''smith'''''_tmgdata.xml should be in your home folder. You now need to change the file extension so as to be able to import it into Gramps. In terminal navigate to your home folder and type:  $ mv converted_'''''smith'''''_tmgdata.xml converted_'''''smith'''''_tmgdata.gramps Open Gramps, create a new family tree, and import the .gramps file you just created. Congratulations! Your TMG data is now in Gramps. {{man note|In coming up with the above instructions,|participants in the [http://sourceforge.net/p/gramps/mailman/gramps-users/ Gramps-Users mailing list] were extremely helpful. The original tmg2gramps [http://www.cohsoft.com.au/tmg2gramps/README.tmg2gramps README] file also provided insight, and the external site [http://www.rhus.org.uk/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}} ==== TMG-Working-Group ====

GEDCOM is currently the Information only option for copying your data out of Family Tree Maker and into GRAMPS. Follow at the instructions above for [[#Standard GEDCOM as transfer tool|Standard GEDCOM]]moment.

GRAMPS can directly import from Genewebhttps://github. Choose ''' File com/girimonti/TMG-> Import ''', select your Geneweb database and choose {{man button|Open}}.Working-Group

=== Ancestrologie = Gramps Addon TMG importer ====

Ancestrologie seems to produce non-standard gedcom for some kinds of dataAn attempt at reading a TMG file Directly from python. In general such problems should be repaired prior to importing into GRAMPS(Does not use TMG's Genbridge). * [[Addon:TMGimporter]] - Not released - Abandoned

==== Programs See {{bug|7591}} for fixing some of the known problems ====Download more details and uncompress (gunzip) to obtain executable scripts. Some additional explanations and data interpretations (or guesses) may be found in the commentstests.

* [http://pub.jgsack.net/g_scripts/fix_Ances_map.pyTMG to GEDCOM includes a template for exporting from TMG into Gramps.gz fix_Ances_map.py.gz] .. script In addition to fix nonthe commonly-standard LATI/LONG PLAC data supported GEDCOM records like people, names, events, families, citations, sources, and exhibits, the template helps produce a GEDCOM that should be in a MAP structure per the 5.5.1 spec.supports:

* [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] .. script to fix various non-standard gedcom usage or gedcom extensions, by converting the otherwise unusable data into a special NOTE entry like: Witnesses and role labels 2 NOTE APPX=Ancestrologie/2007.0.0.761 DATX=_ANCES_XINSEE 75111* Flag values as Gramps Attributes

The data (in this case 75111) may be absent or extend to CONT lines.The non-standard elements converted to APPX notes includeSee {{bug|7591}} and [https:* _ANCES_CLE_FIXE .//www. special internal reference : "Who they are ?"* _ANCES_ORDRE tmgtogedcom.. considered noncom/en/template-critical, events classification * _ANCES_XACTE gramps.. non-critical (certificat found = 1)* _ANCES_XINSEE .. INSEE geographical code (evidently ''simplified 5-digit'htm John Cardinal')* EVEN F .. invalid EVENTS_RECORDED format in a SOUR record* EVEN I .. (same)* LIEU .. a subdivision of place, is not our place but a division* XTYPE .. these seem to be OBJE subordinates* XIDEN .. considered non-critical, media object used for primary media (photo)* XMODE .. " (file is not present at the FILE address)s project ]

'''Users # Partial sources# Repositories are invited to correct/clarify the above information or notify us of additional problems with non standard gedcom or gedcom extensions.'''lost# BAPT, ASSO are lost# Internal numbers are modified

=== AncestryThe GEDCOM generated by WikiTree has a very US-centric dialect of the format. Importing WikiTree GEDCOMs into many programs tends to lose some Name data for individuals.com ===

GEDCOM produced by Ancestry.com is not fully readable by Gramps 2.0.x Their database repeats the <code>NAME</code> data parsed in <code>GIVN</code>, <code>_PGVN</code>, <code>_MIDN</code>, <code>SURN</code> (Given, an occasional custom "preferred given name", a mandatory custom "middle name" field, and 2.2.x (Relationship lostSurname).This is [http:conflicts with the GEDCOM standard form for the <code>GIVN<//wwwcode> data.gramps-project.org/bugsAlthough Gramps does have a "Call name" that corresponds to the <code>_PGVN</view.php?id=899 fixed for 3.0]. Alsocode>, you can use grampify.pl for fixing broken GEDCOM generated by Ancestry.comit does not have a separate Middle Name.

=== ProThe NAME dialect from WikiTree can be converted to a more standard format using a RegEx search and replace script. This is described in the following WikiTree support article:* [https://www.wikitree.com/g2g/1038205/wikitree-Gen ===gedcom-exports-and-lost-middle-names-solved WikiTree GEDCOM Exports And Lost Middle Names: SOLVED] <small>May 2020</small>

Using GEDCOM ====See also====* [https://www.wikitree.com/g2g/1475/how-to -export data -a-gedcom-file-from Pro-Gen is less than ideal. Therefor wikitree How to export a plugin was createdGEDCOM file from WikiTree] <small>Apr 2012</small>* [https://www. The plugin is (as of ddwikitree. 2008com/g2g/1097159/gedcom-import-improvement-to-wt-05from-19) not included in the gramps gedcom import improvement to WikiTree from Gramps distribution, but it is available in ] <small>Aug 2020</small>* [https://www.wikitree.com/g2g/1037716/splitting-gedcoms-with-gramps-a-guide Splitting GEDCOMs with Gramps SVN: A Guide]* [https://www. To download, you can use the following URLwikitree.com/wiki/Space: Splitting_GEDCOMs_-_The_Targeted_Approach#The_Genesis_Filters Splitting GEDCOMs - The Targeted Approach]* [https://grampswww.wikitree.svncom/g2g/search?q=Gramps Gramps mentions in the WikiTree G2G support forum]* [https://www.sourceforgetamurajones.net/svnrootWikiTreeGEDCOM.xhtml WikiTree GEDCOM (third party fix)] <small>Aug 2012 by Tamura Jones</small>* [https:/gramps/trunkwww.wikitree.com/srcg2g/plugins6292/ImportProGen.pydo-you-have-input-on-tag-usage-in-wikitree-gedcom-exports WikiTree GEDCOM revision in response to Tamura Jones]

While it is not part of the normal Gramps distribution it is advised to install it in your personal plugins directory. That directory is normally at ~/.gramps/plugins cd ~/.gramps/plugins wget Source code on [https://gramps.svn.sourceforgegithub.net/svnroot/gramps/trunkcom/wikitree GitHub WikiTree project] for the <code>src/pluginsGedcomExport.php</ImportProGen.pyNext, go to Help -> Plugin Status -code> Reload plugins (or something along these lines)

To import the data Gramps needs to be able to see the Pro== See also =='''Discourse community support forum:'''* [https://gramps.discourse.group/tag/gedcom threads marked as "GEDCOM" related]* Re-Gen directory treeparsing non-uniform date formats: [https://gramps. This all depends on your own setupdiscourse. One possibility is to ZIP everything on your DOS computer and unZIP it on your Linux PC in, say ~group/t/pg30. You may even be running Gramps on a Windows PC and have a copy Promaking-date-input-Gen on that same computer. In the following steps, we're assuming the Promore-Gen files are at ~flexible/pg302814 Making Date Input More Flexible]

You'll see three times a progress bar * [[Other genealogy tools]]* [http://sqlitetoolsforrootsmagic.wikispaces.com/ SQLite Tools for "Individuals", "Families" and "Adding children"RootsMagic]* [http://wiki-en.genealogy. The import process can create warnings and you can look at them by clicking on the net/Category:GEDCOM-Tag GenWiki Category:GEDCOM-Tag] (ioriginally in [http://wiki-de.genealogy.net/Kategorie:GEDCOM-Tag Deutsch]) icon in * 2021 Development note: [[GEDCOM_7_support|GEDCOM 7 support]] (Note that the lower left part of the Gramps windowGEDCOM 7.0. It 2 specification was published 15 Jun 2021 and it is advised typical for revised specifications to copy and save these warnings. There can not be all kinds of reasons supported for these warnings (for example an incorrect datethe first 6 to 18 months.) and you may want to correct the imported data afterwards{{languages|Import from another genealogy program}}[[Category:How do I...]][[Category:Developers/General]]