Migration to Presenter

Moving from WorshipTools Presenter, ProPresenter, EasyWorship, OpenLP, SongBeamer, or another program? Start by moving a few songs, then rebuild one service in ProWeave Presenter and rehearse it. You can keep using your existing software while you prepare.

If you are also moving volunteers, rosters, and service plans, follow Migration to Hub. WorshipTools Presenter and WorshipTools Planning share a song library, so you only need to move each song once before using ProWeave's own song sync.

Choose your starting program

The song importer does not convert complete services, presentation themes, backgrounds, animations, output settings, or volunteer rosters. Copy media separately and recreate the service order and display profiles in ProWeave.

Import and check songs in ProWeave

1. Keep a copy of your source library and your existing ProWeave collection. Use copies of database files, with the source program closed.
2. Open Deck Builder → Library → Lyrics → Import songs. The first-run setup also offers Import songs….
3. Choose Choose files or folder… and select the files prepared below. Start with two or three representative songs.
4. Review every song's title, preview, and warnings. Unselect songs you do not want to import.
5. Leave duplicates on Skip unless you deliberately need a second copy or replacement. Import as new copy keeps a separate song. Replace existing overwrites the local song, has no Presenter undo, and can affect decks that use it.
6. Click the import button. Open the saved songs in Lyrics Designer, check the lyrics and section labels, then drag them from Lyrics into a test deck.

Check verse order and repeated choruses against your original service. The imported song text does not store the source key or tempo (BPM); set these again where needed. Recreate font, slide layout, timing, and arrangement settings too. A warning about missing lyrics means the imported record cannot yet be used to project a song.

WorshipTools

Use the WorshipTools Planning website to access the songs shared with WorshipTools Presenter. ProWeave does not connect to a WorshipTools account or import its cloud database. The documented route is copying the song's editable content; WorshipTools support recommends saving one copied ChordPro source per song. WorshipTools: local ChordPro storage.

Songs with ChordPro

1. In WorshipTools Planning, open Songs, select a song, and choose Edit at the top right.
2. Open Chords and its Edit button to show the ChordPro source. Copy the source, including its title, author, section tags, chords, and copyright details. WorshipTools: ChordPro editor.
3. Paste into a plain-text editor and save one UTF-8 file per song, preferably with the .chordpro extension. On macOS TextEdit, use Format → Make Plain Text before saving. Do not save as a Word document, PDF, or rich-text file.
4. Import those files using the ProWeave steps above. Check the resulting section labels and inline chords, and set key, tempo, and the required song order separately.

Songs with lyrics only

1. In WorshipTools Planning, open the song's Edit → Lyrics area. Copy each section and retain its section name. The lyrics and chord chart can contain different arrangements, so choose the version you intend to use. WorshipTools: editing songs.
2. Save one plain-text .txt file per song: title on the first line, author on the second, a blank line, then labelled sections such as [Verse 1] and [Chorus], separated by blank lines. Copy the copyright and CCLI song number too.
3. Import the files, or paste one song into Lyrics Designer and save it. Review every slide before presenting.

Use this structure for a .txt file. The words and metadata below are an invented example; replace them with your song's actual information, and omit the CCLI line when it has no CCLI song number. Keep the copyright and CCLI lines together at the end, separated from the lyrics by a blank line.

Morning Song
Example authors

[Verse 1]
We gather here this morning
With a song of hope to share

[Chorus]
Together we will sing

© 2026 Example authors
CCLI Song ID: 1234567

WorshipTools Planning also offers Songs → Export list, which downloads CSV. Use it as a checklist of songs to move. You can scan it in ProWeave for recognised title, author, and CCLI columns, but a list without a lyrics column imports only metadata. It does not recover lyrics, slide designs, or services. WorshipTools: song-list export.

For songs you obtain through SongSelect, you can instead download the permitted lyrics .txt files from SongSelect and import them through Library & sources.

ProPresenter

1. Select the song presentations in ProPresenter's Library and use File → Export → Presentation. Save individual .pro files for ProPresenter 7, or use .pro4, .pro5, or .pro6 files from the older versions.
2. Import those files in ProWeave. Choose presentation files; ProWeave's song importer does not accept ProPresenter playlist, bundle, or theme files.
3. If a file cannot be read, use ProPresenter's Export Text and import the resulting .txt song instead. Keep separate files for separate songs. ProPresenter: exporting files.

ProPresenter 7 import extracts readable song text where possible; slide groups, labels, arrangement order, and repeated slides may not survive the conversion. Compare the complete imported text with the source. Recreate media cues, themes, and service playlists in ProWeave. The import preview reports content it cannot preserve.

EasyWorship

1. In EasyWorship, open Profiles → Profiles Manager, select the profile, and open its Instance Location. Find the version folder and Databases → Data. EasyWorship: locate profile data.
2. Close EasyWorship, then copy the database folder to a migration folder. Keep Songs.db together with SongWords.db or SongWords.dat; copying only song titles is insufficient when the lyrics are in the companion file.
3. Select the copied files or folder in ProWeave's song importer. This route supports the EasyWorship 6.1 / 7 database family. Earlier databases need conversion in EasyWorship or a supported text export first.
4. Review the song previews. Copy images, videos, and audio from the original resources separately through Library → Media.

OpenLP and OpenLyrics

1. In OpenLP, choose File → Export → Song, select the songs, choose a destination folder, and finish the export. This produces an OpenLyrics XML file per song. OpenLP: exporting songs.
2. Select that folder or the .xml files in ProWeave. A .zip containing OpenLyrics XML is also supported. An OpenLP songs database (.sqlite or .sqlite3) is an alternative; close OpenLP before copying it.
3. Check verses, authors, copyright, and arrangement order. OpenLP service and theme files are not song imports.

SongBeamer

Copy the .sng song files you use in SongBeamer into a migration folder, then select that folder in ProWeave's song importer. These are song files, not SongBeamer schedule files. Check multilingual text, section breaks, and copyright after import. Add backgrounds and rebuild the schedule separately.

ChordPro, text, and other programs

• ChordPro: import .cho, .chordpro, .chopro, .chord, or .crd. A .txt file containing ChordPro directives can also be detected as ChordPro.
• Plain text: use one .txt file per song, with title, author, and labelled sections as described above.
• CSV: use a header row with recognised columns such as title, author, ccli, copyright, and lyrics. Quote multiline lyrics correctly. Without lyrics, the result is a song record to complete manually.
• Proclaim or another program: use an available text or ChordPro source, or copy editable lyrics into the plain-text structure above. ProWeave does not import that program's native service files. A usage report or song-title list is not a lyric library.

Finish the move to the suite

Import your images, videos, audio, and PDFs through Library → Media, then build one service in Deck Builder. Check all displays, rehearse the whole service, and test offline playback before your first live service.

To use the imported songs in ProWeave Hub, keep the collection open, sign into the intended organisation, and choose Connections → Hub → Sync songs with Hub. Review duplicates and the organisation's song allowance; free Hub permits up to 3 songs, while Team removes that cap. Song sync and building a deck from a Hub event are separate actions. Continue with Migration to Hub for people and plans.