Mainfolk

Fire departments

Before You Move: Save Your Calendar, Documents and Forms

Before You Move: Save Your Calendar, Documents and Forms

Photo by Robert So on Pexels

Save the parts people use most

If your department is moving to a new website, the goal is simple: keep the public useful, keep the office from answering the same questions over and over, and make sure visitors can still find the things they need. The safest approach is to treat the move like a records check, not a redesign.

Start by saving the items that people look for most often. For a fire department, fire district, ladies auxiliary, or exempt fire association, that usually means the calendar, public documents, forms, staff or officer pages, and the about page. Those are the pages that help a resident, volunteer, vendor, or reporter understand who you are and what is happening next.

Think of it this way: if someone is trying to find the next meeting, download a permit form, or confirm who to contact, those pages do the work. If they disappear during a move, your inbox and phone usually pay the price.

What to keep from the calendar

Save the full calendar, not just the current month. Even if some items will change later, the old entries often show what kinds of events and meetings your department has, and they help you rebuild the new calendar faster.

Check for recurring items too. Examples: monthly board meetings, training nights, blood drives, pancake breakfasts, drill days, open house events, or ambulance standby schedules. If your old site had a way for visitors to print or view details by month, make sure that information comes over in a clear, readable way.

Also save any calendar labels that matter to your community. A meeting marked “public,” “board,” or “station event” is more useful than a calendar full of vague titles.

Save public documents and forms as separate items

Do not rely on one big download folder and hope people will figure it out later. Save each important document and form on its own, with a clear name and a short note about what it is for.

Useful examples include:

  • meeting agendas and minutes
  • permit or burn forms
  • membership applications
  • hall rental forms
  • public notices
  • budget or annual report documents
  • inspection request forms

If a form is used often, save the version people actually use. A form that is hard to open, hard to print, or missing a field creates extra work for your team later.

For document files, check that the wording still makes sense to a visitor who did not help build the old site. A file named “doc1” helps no one. A file named “station_rental_form” or “march_board_minutes” is much easier to manage.

Do not forget the staff and about pages

The about page is more than a nice extra. It often answers the question people really have: who are you, what do you serve, and how do I reach the right person?

Save names, titles, phone numbers, email addresses, station locations, service area notes, and any short description of your department or organization. If you list officers, board members, chiefs, or auxiliary leaders, keep that structure the same unless you are ready to update it at the same time.

That matters because visitors use these pages to make a decision quickly. Example: a resident wants to know whether to call the main station number or a board chair. A vendor wants the right contact for invoices. A volunteer wants to know who handles applications. If those pages are missing or outdated, the message gets lost.

Save photos, but only the ones that still help

Photos can make a new site feel familiar, but not every image belongs in the move. Save the photos that show your people, station, equipment, events, and community work in a way that still reflects the department today.

Before you carry everything over, sort the photos into three groups:

  • keep and reuse
  • keep for records only
  • leave out

Examples of good keeper photos: station exterior, apparatus, award nights, open houses, recruiting events, training scenes, and group photos that still reflect current leadership or teams. Remove blurry images, duplicate shots, and anything that no longer matches how you want to present the department.

If a photo has an important caption, save that too. A picture without a label may look nice, but it may not tell visitors anything useful.

How to check that nothing was left behind

Once the new site is ready to go live, do a page-by-page check before you announce it. This step catches the things that are easy to miss: an old form that never came over, a broken page title, a meeting notice buried in the wrong place, or a contact page that no longer points to the right person.

Use this simple check:

  1. Compare the old site’s main navigation with the new one.
  2. Open every calendar page and make sure the events still show up clearly.
  3. Download each public document and form from the new site.
  4. Check the about page, staff page, and contact page for current names and numbers.
  5. Look through the photo pages and confirm the images still make sense.
  6. Search for the most common requests your visitors make, and see if the answers are easy to find.

It helps to have one person who knows the old site well and one person who does not. The first person can spot what was missing. The second person can tell you whether the new version is easy to use.

If your department has heard that your current provider is winding down, confirm your own date with them directly. Mainfolk is not affiliated with 911Webs and does not know any department’s date. If you are looking for a website service for fire departments and public safety organizations, the important thing is to make the move with your own content, on your own terms.

A quick final pass before launch

Before you go live, ask these plain questions: Can a visitor find the next meeting in under a minute? Can they download the form they need? Can they find the right contact without guessing? If the answer is no, fix that before launch.

For departments and associations, a good move is not about changing everything. It is about keeping the useful parts, cleaning up the confusing parts, and making sure the public can still get what they need without calling for help.

Mainfolk can handle the move for you, including free migration of public content, while you keep your own web address and can export your content anytime.

Free download: grab our fire department website checklist: the short, plain-English list of what your site needs to get found and bring in calls. No cost, no obligation.

Common questions

What should we save first when moving our department website?

Start with the calendar, public documents, forms, staff or officer pages, and the about page. Those are the pages people use most and the ones that create the most follow-up questions if they go missing.

How do we know nothing important was left behind?

Compare the old and new site page by page, open every form and document, and test the most common visitor questions. It also helps to have someone familiar with the old site and someone new to it review the final version.

Should we move every photo from the old site?

No. Keep the photos that still help people understand your department and leave out blurry, duplicate, or outdated images. Save captions too if they explain the photo.

← All posts

Want a site like the one we just described?

Accessible by construction. Live in days. No contract, no RFP.