From spreadsheets to Lodge software: migrating without losing history

Most Lodges do not start from nothing. They start from a spreadsheet that has been passed down three Secretaries, a folder of scanned minutes, and a Treasurer's workbook that only he fully understands. Moving that into a system is less about the software than about deciding what deserves to come along.

This guide is the order we have seen work, and the mistakes that cost Lodges a month.

First: separate the record from the archive

Not everything needs migrating. Ask of each thing you hold: does the Lodge need to act on this, or does it need to be able to find it?

• The record — the current roll, standing, degrees, offices, open charges. This has to be live in the system, accurate on day one.
• The archive — minutes from 1994, old correspondence, scanned certificates. This can be uploaded gradually, or left where it is and indexed later.

Lodges that try to migrate both at once usually stall on the archive and never finish the record. Do the record first, completely. The archive will still be there.

The roll is the hard part, and it is not technical

Every Lodge discovers the same thing when it imports the roll: the spreadsheet disagrees with reality. Brethren who demitted years ago are still listed. Degrees are missing dates. Two rows are the same man, spelled differently. One brother has no membership number because nobody ever filled it in.

This is not a migration problem — it is an existing problem that the migration makes visible. Budget an evening for the Secretary and one other officer to go through the roll line by line before importing anything. It is the single highest-value hour in the whole project, and it is the one most often skipped.

A workable order

1. Clean and import the roll. Names, membership numbers, degrees with dates, contact details, standing. Verify the count against the Grand Lodge return before going further.
2. Set up access. Who is Secretary, who is Treasurer, who sits in the East. Get this right before anyone else logs in, because it determines what each brother sees.
3. Open the books. Enter the current balance and the open charges — not the entire financial history. The books start clean on a known date; the old workbook remains as the record of everything before it.
4. Put the calendar in. The year's communications, with the degree each one requires. From here the Lodge starts using the system rather than preparing it.
5. Bring brethren in. Not on day one. Let the officers use it for a month first, find what is wrong, fix it, and then invite the Lodge — an opening night with broken data costs you the room's goodwill for a year.
6. Then the archive, at whatever pace suits.

What usually breaks

• Dates in the wrong format. A spreadsheet that has been edited by six people has dates in four formats. Standardize before importing, not after.
• Duplicated brethren. Almost always caused by a name spelled two ways. Match on membership number, never on name.
• Missing membership numbers. Chase them before the import. A record without one is a record you cannot reconcile with the Grand Lodge later.
• Financial history imported half-way. Either bring a period in complete or start fresh from a date. A partial year produces reports that are wrong in a way nobody notices for months.

Who should run it

Two brethren, not one. The Secretary, because the roll is his, and one other officer who can check his work — the second pair of eyes is what catches the duplicated brother and the demitted member still on the list. A Lodge that hands the whole project to its most technical brother usually ends up with a system only he understands, which is the problem it was trying to solve.

How long it takes

For a Lodge of fifty to eighty brethren with a spreadsheet in reasonable shape: an evening to clean the roll, an evening to import and set up access, and a month of the officers using it before the Lodge is invited in. The archive takes as long as it takes.

If you are still deciding between options, the checklist for choosing Lodge software covers what to evaluate first — including whether you can get your data back out, which matters far more on the day you leave a platform than on the day you join one.