Migration, step by step
- In Paratext 7, make sure every team member who can change text or add notes (administrators, translators, consultants) does a send/receive.
- Do a send/receive so your computer has all the latest changes. Tell everyone not to do any work in Paratext 7.
- In Paratext 8, go to File > Open Project/Resource. Make sure the box at lower left “Show Paratext 7 projects” is checked.
- Select your project.
- v7 means Paratext 8 sees it in the Paratext 7 projects folder.
- Unregistered means it isn’t registered for Paratext 8.
Your project could be registered already for Paratext 8 if
- it was listed as an important project to be pre-registered
- you had already migrated and registered it for Paratext 8 and you are now doing a re-migration.
- Click OK.
Paratext will open the migration dialogue box. If necessary, it will prompt you to register it.
- If your project is registered, but listed as a Test or Training Project, click on Manage registration… in order to change the designation to “Standard”
- If your project is already registered, skip to Migration below
Click Register Online.
The registry form should appear (picture below of first section). Paratext 8 will copy the project short name (Paratext project on the form) and the project full name from the Paratext 7 project. The registration form shows which fields are required, by displaying a red asterisk. Later you can change the project full name but you cannot change the project short name.
Description: add more information here if you wish to. There are also fields for more information about the project in the second part of the form.
Language: The language name has to match an entry in the Ethnologue database. Click the “Advanced” box to fill in more information if you need to distinguish the language of your project from the language with that ethnologue code. The advanced form looks like this, where choices you select under Script, Region or Variant add extra letters and numbers to the identifier.
Scope refers to which books you intend to translate, for example the whole Bible, New Testament, Whole Bible plus Deuterocanon, Portions, etc.
Translation Type: choose First if this is the first translation in this language, choose Revision if it is a revision of a previous translation, choose New if it is a new translation but a previous translation does exist for the language.
Country select the country or countries where this translation is intended to be used.
Rights holder choose from the list the likely rights holder for this translation. If the eventual rights holder is an organization yet to be formed or recognized, choose something from the list and edit the registration later.
More information The second section of the registration form contains several places you can add supplementary information about your project. None of these fields are required.
- Standard is the default choice. Information about the project is not available to the public, but only to registered Paratext users within the same organization.
- Test or Training is good for testing projects, or projects you only create to use in a training program or workshop.
- Confidential is for situations where entering information about your project online is a security concern. Information is restricted to members of the project and to those who manage the registration data for the organization.
The last requirement for registration is to indicate that you will comply with the Forum of Bible Agencies International translation guidelines (a link is provided) and that you agree to keep a backup copy of your project in the Digital Bible library. The Digital Bible library will not share your project with anyone without your express permission.
When finished filling out the registration information, click Submit Registration. If the information is complete, the site should tell you that the registration was accepted, and when you go back to Paratext, it should have detected that the project is now registered.
If later you wish to update or change your project registration, in Paratext you can go to Project > Project Properties and Settings and click the Manage registration link at the bottom of the General tab. Or you can go in your web browser to registry.paratext.org, find your project and click “Edit”.
Migrating the project
If you are migrating a project that is already registered, the migration dialog should show this:
If Paratext is saying registration is required, click on the Register Online link and follow the steps described above in registration.
The five check boxes in the Migrate project data section are items you need to check off before the migration can proceed. These are similar to the checkboxes you had to check when you first set up your project for send/receive, and the motivation for them is similar. We want to be sure your team knows about and is planning on migrating, that you have all the latest changes on your computer, and that everyone knows the project should not be edited any more in Paratext 7 after migrating, Check these boxes if you are ready, then click “Migrate now”. “Migrate later” is not an option to schedule the migration for a later time, it is the way to back out of the migration dialog without doing anything if you are not ready to migrate now.
When you click “Migrate now”, Paratext 8 should copy the project to your Paratext 8 folder and do a send/receive. So when the migration is finished, the project should be on the server so team members can send/receive to get a copy of the newly migrated project.
Paratext 8 is able to check if the Paratext 7 project on your computer has new changes since the last send/receive. If it detects this, it gives you a warning.
If you get the warning, click OK which stops the migration process, do your send/receive in Paratext 7, then restart the migration by selecting the Paratext 7 project in the project list.
Migrating multiple projects
If you have multiple project to re-migrate, you will have to delete them one by one. You can select several projects for migration, by using Ctrl click to highlight several. This will line them up for migration, for each one you’ll have to check off the five boxes that you are ready to migrate, and submit registration if it is required. If you have projects dependent on others, such as back translations or daughter translations, it is best to migrate the source or parent project first.