GEDCOM

[Ewan]

Regarding transferring information from one family history program to another.  In very very basic terms how would you transfer this information from one program to another one.
Thank you

[Mart 'n' Al]

Your current program will almost certainly have a menu option to export your gedcom file.  Use that option.

Your new program will almost certainly have a menu option to import your gedcom file. Use this option, navigate to the saved file and import it. It is very easy.

If that isn't totally clear, specify the two programs in your next message.

Martin

[arthurk]

Martin posted while I was typing - this expands on what he wrote:

Often you create a Gedcom file with an Export menu option, and you then have to Import it in the new program. However, a couple of caveats come to mind - others might think of more:

(a) the Export and Import functions might come with options relating to things like private information, fact types that you've defined, which version of Gedcom, etc, so read the Help files carefully. I would probably start with the receiving program, to find out what it needs from the exporting one.

(b) some programs can do a direct import of the normal file types created by other programs, and where this is available it's probably less prone to error than using Gedcom.

The important thing is to read the instructions and be prepared to experiment with different settings, then examine the imported file closely to see how it's gone. As well as custom fact types and private information, things that can be problematic because of the way different programs handle them include places and addresses; notes attached to almost any person/fact/source etc; witnesses to events; and maybe others.

Keep backups from the old program, and if possible keep the program itself for a few months until you're sure no data has got lost or corrupted in the move. Of course, the smaller your file the easier it will be to check for errors; with a large file there's an element of trust, so it's worth identifying potential problem areas before you start.

If you'd like to tell us which program (and version) you are planning to move from and to, someone should be able to give you more detailed advice.

[Palladium]

...Remembering that the gedcom is data in text form and can be looked at (and edited if you are brave!) in Notepad. Don't expect to carry across more information than just that...

Pall

[arthurk]

There's a similar post from Ewan at https://www.rootschat.com/forum/index.php?topic=820650.0

To save duplication I've asked for discussions about the Gedcom transfer to be kept to this thread, but it looks as though Ewan hasn't chosen his new program yet.

One more question for Ewan:
How many people are there in your database? This is to help us judge how feasible it would be to do any post-import checking and tidying.

[Craclyn]

Also be aware that the export to a gedcom file may need you to decide the starting person in the tree before you begin. In some cases you can set paramaters, such as all profiles, limited number of generations, just direct line, etc.

[Ewan]

Thank you all for your help and advice, this sounds like a nightmare.  I will respond in due course.

Thank you again

[[Ray]]

Hi
I already have one of Ewan's files.
Successfully created v5.5 gedcom and another different version, plus .csv
Have ( poss minor) problem sending converted files to Ewan.

Ray

[[Ray]]

...Remembering that the gedcom is data in text form and can be looked at (and edited if you are brave!) in Notepad. Don't expect to carry across more information than just that...

Pall

There is a method for CSV intermediary file, therefore editting/saving in spreadsheet  "format" is possible.