Changes

There are several ways to import your family tree into GRAMPS Gramps from another program. The best way depends on what program you want to copy the information from.

== GRAMPS Gramps to GRAMPSGramps==

This is the easy one. The simplest and safest method to move all your information from one GRAMPS Gramps program to another on a different computer is to choose {{man menu|Family Trees -> Export}} from the first GRAMPSGramps. Follow the instructions, choosing {{man label|GRAMPS Gramps Package}} for the format to save. And do not forget to disable privacy filter.

Copy the file created by GRAMPS Gramps to the destination computer. Then in its GRAMPSGramps, choose {{man menu|Family Trees -> Import}} and select the transferred file.

{{man warn| Check The Results |Check your data carefully once imported into GRAMPSGramps. 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. GRAMPS Gramps aims to support the GEDCOM 5.5. 1 standard.}}

Take special attention that == Spreadsheet import == Although the following is not a standard format, as a last resort you could also construct a spreadsheet format of your media files are transferred toodata 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 found by GRAMPSnotes. In the menu {{man menu|Tools It does import/export birth, death, and marriage events---> Utilities}}and notes for those events, you will find the {{man label|Media Manager}}people, with which you can change the path of your media objects and marriages.  For more details on this format see [[Gramps 4.2 Wiki Manual - Manage Family Trees: CSV Import and Export]]. == Addon == [[GEDCOM Extensions]] should be able to the new path if neededhandle unofficial GEDCOM extensions.

Ancestrologie seems to produce non-standard gedcom for some kinds of data. In general such problems should be repaired prior to importing into GRAMPSGramps.

* [http://pub.jgsack.net/g_scripts/fix_Ances_x1.py.gz fix_Ances_x1.py.gz] .. script to fix various non-standard gedcom GEDCOM usage or gedcom GEDCOM extensions, by converting the otherwise unusable data into a special NOTE entry like:

In addition, one other change, replaces a non-standard "FILA" item to the gedcom GEDCOM 5.5.1 generic FACT item (in INDIVIDUAL_ATTRIBUTE_STRUCTURE) provided for exactly this kind of data.

'''Users are invited to correct/clarify the above information or notify us of additional problems with non standard gedcom GEDCOM or gedcom GEDCOM extensions.'''

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

====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... ====Specific instructions for FTM2005:====

* Character set: ANSI (GRAMPS Gramps will convert to UTF-8 upon import)

The [http://gramps-project.org/wiki/index.php?title=[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.

[http://gramps-project.org/wiki/index.php?title=Import_from_another_program[Import_from_another_genealogy_program#tmg2gramps |tmg2gramps]] might help for generating a [http://gramps-project.org/wiki/index.php?title=GRAMPS_XML [Gramps XML]] file, which could preserve more data.

GRAMPS 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}}.

According to a [http://www.arvernes.com/wiki/index.php/Ancestris_-_Rapports_-_Boite_%C3%A0_outils_-_R%C3%A9paration_GedCom#Heredis "''Ancestris ''" wiki], GEDCOM generated by Heredis may :

According to a [http://www.arvernes.com/wiki/index.php/Ancestris_-_Rapports_-_Boite_%C3%A0_outils_-_R%C3%A9paration_GedCom#Legacy "''Ancestris ''" wiki], GEDCOM generated by Legacy may :

For many people, using GEDCOM will lose too much information. If this is the case for you, you might like to try [http://www.cohsoft.com.au/tmg2gramps/ tmg2gramps], though it is aimed at advanced usersmost notably "Witness" information.

You'll see three times a progress bar If this is the case for "Individuals"you, "Families" and "Adding children"you might like to try [http://www. The import process can create warnings and you can look at them by clicking on the (i) icon in the lower left part of the GRAMPS windowcohsoft.com.au/tmg2gramps/ tmg2gramps]. It Though it is advised to copy and save these warnings. There can be all kinds of reasons for these warnings (for example an incorrect date) and you may want to correct a little more involved, the results are often worth the imported data afterwardsextra 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 it tmg2gramps [[Media:Tmg2gramps.tar.gz|here]]. tmg2gramps was designed to, '''"...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 there 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. ===== Known issues =====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 -- 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" -- 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 -- 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_4.1_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. ===== 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> ====== 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://homepage.ntlworld.com/hamamelis/linux/tmg2gramps.htm 'TMG to GRAMPS how I did it using tmg2gramps script'] provided the initial inspiration.}} ==== TMG-Working-Group ==== Information only at the moment. '''Project focused on technical aspects related to the continued use, data migration and extension of The Master Genealogist software. The target audience are software developers who wish to participate in an open source project.''' ''Bill Girimonti'' https://github.com/girimonti/TMG-Working-Group ==== tmgviewer ==== An attempt at reading a TMG file Directly from python. (Does not use TMG's Genbridge). * [[Addon:TMGimporter]] - WIP - Not released yet. See {{bug|7591}} for more details and tests.

According to a [http://www.arvernes.com/wiki/index.php/Ancestris_-_Rapports_-_Boite_%C3%A0_outils_-_R%C3%A9paration_GedCom#Visuged "''Ancestris ''" wiki], GEDCOM generated by Visuged 8.40.0 seems to definitively corrupt your data !

== Spreadsheet import See also ==* [[Other genealogy tools]]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* [http://sqlitetoolsforrootsmagic. The CSV import option currently doesn't allow import of all GRAMPS datawikispaces. For example, it doesn't import all of a person's events and notes. It does importcom/export birth, death, and marriage events---and notes SQLite Tools for those events, people, and marriages. For more details on this format see [[Gramps 4.0 Wiki Manual - Manage Family Trees: CSV Import and Export]RootsMagic].