# Dev Diary 96 - Import Classic Projects into Elements

**URL:** <https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180>\
**Category:** Elements\
**Created:** [August 25, 2025, 3:29pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180 "2025-08-25T15:29:26Z")\
**Posts on this page:** 20\
**Page:** 4

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [August 27, 2025, 12:36pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/61 "2025-08-27T12:36:16Z")

</div>

> [@Marcellus](#):
>
> However the only thing I really need before I upload and replace the Classic version with an Elements version is an easy way of setting up a private members page with a password.

We’ve been exploring this internal and with the backend we created for the Form/CMS part of Elements we think this would be very doable. However, I have a few questions for you…

What do you currently use? and what are the essential features you need for a “private members page”? Do you just want to protect a page with a single password? or do you need more features?

---

<div class="post-metadata">

**Author:** ![karent](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@karent](https://forums.realmacsoftware.com/u/karent)\
**Post date:** [August 27, 2025, 1:44pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/62 "2025-08-27T13:44:42Z")

</div>

Moving sites is the one thing stopping me from switching to Elements because of the time involved . I’d settle for structure as shown in the video, but if there’s some way of retaining at least some of the style settings, that would be a godsend.

Thanks!

KT

---

<div class="post-metadata">

**Author:** ![logrunner](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@logrunner](https://forums.realmacsoftware.com/u/logrunner)\
**Post date:** [August 27, 2025, 3:35pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/63 "2025-08-27T15:35:58Z")

</div>

> [@dan](#):
>
> What do you currently use? and what are the essential features you need for a “private members page”? Do you just want to protect a page with a single password? or do you need more features?

@dan I know you weren’t asking me but … 😀

I am using [Sitelok from Vibralogix](https://www.vibralogix.com/sitelokpw/) (which is Elements friendly as it has Elements Components) for my site which has private members pages where each member has their own id and password. This is a very comprehensive solution.

For a more basic function, I would think it would be useful to provide a similar function to the RW Classic Page Safe stack which is quite simple compared to what Sitelok offers.

I used Page Safe until I “upgraded” to Sitelok. 🙂

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [August 27, 2025, 5:42pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/64 "2025-08-27T17:42:22Z")

</div>

Good news 🎉 [Elements 1.2 is now live](https://forums.realmacsoftware.com/t/elements-1-2-0-23816/50281), it includes a beta of the Classic Project Import feature.

Please take it for a spin, and let us know what you think!

---

<div class="post-metadata">

**Author:** ![Marcellus](https://avatars.discourse-cdn.com/v4/letter/m/b782af/32.png) [@Marcellus](https://forums.realmacsoftware.com/u/Marcellus)\
**Post date:** [August 27, 2025, 11:25pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/65 "2025-08-27T23:25:39Z")

</div>

Hi Dan, Good morning from Australia. Thanks for getting back to me so quickly. I use PageSafe and a simple 7 digit password to allow members to access the private page. The page contains things like members contact details, meeting minutes, newsletters etc. I don’t need anything complicated just something to keep these sort of things private.  
Thanks,  
Ken  
PS I have attached the website address or one of my sites to give you an idea of what I need.

Ken Farrow  
Secretary  
Lions Club of Torquay  
[torquaylionsclub@icloud.com](mailto:torquaylionsclub@icloud.com)

---

<div class="post-metadata">

**Author:** ![Marcellus](https://avatars.discourse-cdn.com/v4/letter/m/b782af/32.png) [@Marcellus](https://forums.realmacsoftware.com/u/Marcellus)\
**Post date:** [August 27, 2025, 11:30pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/66 "2025-08-27T23:30:34Z")

</div>

Hi Dan, Good morning from Australia. Thanks for getting back to me so quickly. I use PageSafe and a simple 7 digit password to allow members to access the private page. The page contains things like members contact details, meeting minutes, newsletters etc. I don’t need anything complicated just something to keep these sort of things private.  
Thanks,  
Ken  
PS I have attached the website address or one of my sites to give you an idea of what I need.

Ken Farrow  
Secretary  
Lions Club of Torquay  
torquaylionsclub.org.au

---

<div class="post-metadata">

**Author:** ![guywoodland](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/guywoodland/32/37481_2.png) [@guywoodland](https://forums.realmacsoftware.com/u/guywoodland)\
**Post date:** [August 28, 2025, 6:54am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/67 "2025-08-28T06:54:47Z")

</div>

Dan the video is useful in terms of showing how the structure can be recreated but do think to import content would be really important as well?

The other thing I couldn’t figure out is to do with CMS. 99% of websites I have built use classic, stacks, f6 and total CMS. How could this work?

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [August 28, 2025, 8:59am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/68 "2025-08-28T08:59:40Z")

</div>

> [@guywoodland](#):
>
> The other thing I couldn’t figure out is to do with CMS. 99% of websites I have built use classic, stacks, f6 and total CMS. How could this work?

Elements can replace those 4 other separate systems for you (classic, stacks, Foundation, and total CMS), and working in one cohesive environment has many advantages 🙂

I think the best way to get started is to build a test project in Elements, download the trial, play around see how you get on, then come back and ask any specific questions.

Regarding the CMS, the basics are usable, but it is still in development. We’re also working on writing the documentation, doing videos, and finishing the other CMS components.

Hope that helps.

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [August 28, 2025, 9:00am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/69 "2025-08-28T09:00:06Z")

</div>

> [@Marcellus](#):
>
> I use PageSafe and a simple 7 digit password to allow members to access the private page. The page contains things like members contact details, meeting minutes, newsletters etc. I don’t need anything complicated just something to keep these sort of things private.

Perfect, that’s good to know!

---

<div class="post-metadata">

**Author:** ![PMUK](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@PMUK](https://forums.realmacsoftware.com/u/PMUK)\
**Post date:** [August 28, 2025, 2:28pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/70 "2025-08-28T14:28:40Z")

</div>

Just got in and updated and tried new importer. It crashed on 3 projects and I’ve sent crash reports. I can not get it to work on my own projects. Tried loading one of the sample projects it comes with and bobs your uncle it worked. So here’s my question, I converted most of my sites from RW8 to Classic when I got it so ids this the problem? They’re not pure native classic projects? TIA

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [August 28, 2025, 2:50pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/71 "2025-08-28T14:50:28Z")

</div>

@PMUK We may have already fixed the issues that are affecting your projects… Can you send them over so we can ensure the new build we’re preparing works with your projects - [forumsupport@realmacsoftware.com](mailto:forumsupport@realmacsoftware.com)

---

<div class="post-metadata">

**Author:** ![PMUK](https://avatars.discourse-cdn.com/v4/letter/p/7993a0/32.png) [@PMUK](https://forums.realmacsoftware.com/u/PMUK)\
**Post date:** [August 28, 2025, 3:05pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/72 "2025-08-28T15:05:08Z")

</div>

If you have fixed this as this is a major game changer. A lot of people on another forum moaned about Classics being a “subscription” set up and they were staying with RW8 and if you can get these into ELEMENTS as well then WOOOOOWWW!

---

<div class="post-metadata">

**Author:** ![ctdkite](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ctdkite/32/17717_2.png) [@ctdkite](https://forums.realmacsoftware.com/u/ctdkite)\
**Post date:** [August 28, 2025, 5:43pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/73 "2025-08-28T17:43:41Z")

</div>

It is a good start. What makes me hesitate is that we are a small nonprofit organization, but our website has hundreds of pages. Recreating the website in Elements and then moving all the content - typically Stacks with text and images - into Elements seems daunting. What’s worse that I am now retired and the new guy knows enough about Classic to duplicate a page and them add new content. I will give the import features a try, though.

---

<div class="post-metadata">

**Author:** ![pumpkin](https://avatars.discourse-cdn.com/v4/letter/p/ccd318/32.png) [@pumpkin](https://forums.realmacsoftware.com/u/pumpkin)\
**Post date:** [August 28, 2025, 7:59pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/74 "2025-08-28T19:59:12Z")

</div>

I’m thinking especially of structured data here, plus some sort of SEO checklist or automated checker (incl. checking for duplicate pages - like index.html and index.php in the same folder, or duplicate SEO content) before publishing, that reminds of missing essential SEO data. And proper 404 handling, if that’s something that can be handled from within elements.

---

<div class="post-metadata">

**Author:** ![Fuellemann](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/fuellemann/32/22871_2.png) [@Fuellemann](https://forums.realmacsoftware.com/u/Fuellemann)\
**Post date:** [August 29, 2025, 8:12am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/75 "2025-08-29T08:12:53Z")

</div>

Basically we need the functionality of the SEO helper stack, which is used in RW&Stacks.

---

<div class="post-metadata">

**Author:** ![Lion](https://avatars.discourse-cdn.com/v4/letter/l/57b2e6/32.png) [@Lion](https://forums.realmacsoftware.com/u/Lion)\
**Post date:** [August 29, 2025, 10:00am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/76 "2025-08-29T10:00:13Z")

</div>

Hi Dan, Thanks for this feature. I think it is great.

I do just want to say that as up to now I have been building all Classic projects from scratch in Elements and here is what I have found:

1. In building from scratch it has given me the time to discover how Elements works and how all the component settings work. I do realise that not everyone has the time to do this, but since Classic is fully functional, I don’t feel rushed to get the project done because I can still continue making changes and updates through Classic until the Elements project is done.
2. As I progress I can see my development time is getting shorter and I can work faster. The core components help too.
3. Sure, currently there are some things that are missing in Elements that I am currently using in Classic/Stacks, but I do believe that this will be adjusted with time (Or one can find a new of doing).
4. Being able to import meta and SEO etc is great, but what I have also seen is that this is a good time to re evaluate your SEO per project etc.

Thanks for all the work

---

<div class="post-metadata">

**Author:** ![Lion](https://avatars.discourse-cdn.com/v4/letter/l/57b2e6/32.png) [@Lion](https://forums.realmacsoftware.com/u/Lion)\
**Post date:** [August 29, 2025, 10:02am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/77 "2025-08-29T10:02:29Z")

</div>

This will be a good addition in Elements. I am using Sentry.

---

<div class="post-metadata">

**Author:** ![abelragen](https://avatars.discourse-cdn.com/v4/letter/a/bbe5ce/32.png) [@abelragen](https://forums.realmacsoftware.com/u/abelragen)\
**Post date:** [August 29, 2025, 8:26pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/78 "2025-08-29T20:26:46Z")

</div>

Any tools for importing a Classic site into Elements will help, and the more extensive they are, the better.

---

<div class="post-metadata">

**Author:** ![APSS](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/apss/32/30562_2.png) [@APSS](https://forums.realmacsoftware.com/u/APSS)\
**Post date:** [August 30, 2025, 12:47pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/79 "2025-08-30T12:47:26Z")

</div>

Classic:

I started building websites about five years before I found RapidWeaver — yes, even before version 2 — when I was struggling to make WordPress work as something other than a blog site, i.e. to make it more static. Not to mention a website host that charged per page, which were more geared towards big corporations!

I held my breath when the four guys from southern Wales decided to stop developing RapidWeaver as an Apple application and develop their own platform. It worked seamlessly.

In other words, I have been faithful to RapidWeaver from the beginning. No coding required. No need to worry about Tailwind or Bootstrap… just build!

Among the thousands spent on themes, stacks, plug-ins and so on, I purchased Foundry, but found that my page designs rarely worked as I had anticipated. Then came Ulkit-3, with which I have built the most amazing sites that have garnered compliments about how professional they look.

When I recently wrote that I intend to stick with Classic, people wished me well but suggested that I move to Elements. It’s not that simple.

I am a book publisher. I publish books. I also build sites for one corporation (with dozens of sub-domains for each HTML book) as well as weekly blogs.

In other words, I don’t have time to worry about whether Elements or Classic works right now. The truth is that, with all my publishing workload, I have not yet had the time to look at Elements, much less take a closer look. The prospect of engaging with any form of coding is enough to cause me to experience a state of extreme anxiety.

I love Ulkit-3, which comes with demo sites from which I can simply copy and paste any design elements I like.

If and when Elements allows me to seamlessly transfer my numerous Ulkit-3 sites and spares me the word ‘coding’, I will stop holding my breath (well, I’m not) and make the leap.

I will stay with RapidWeaver, which is not free. We are told that Classic is not going anywhere. However, I have found that there is no support for Classic users. I sent in a question more than two weeks ago and have not received a reply. It seems that all support is directed towards Elements users. My two-user renewal is coming up soon, so there is much to think about.

---

<div class="post-metadata">

**Author:** ![dan](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/dan/32/28516_2.png) [@dan](https://forums.realmacsoftware.com/u/dan)\
**Post date:** [August 30, 2025, 5:31pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/80 "2025-08-30T17:31:27Z")

</div>

> [@APSS](#):
>
> I sent in a question more than two weeks ago and have not received a reply.

So sorry you’ve not had a reply. this certainly shouldn’t be the case, we do our best to reply to all emails within hours, or days at most (if it’s over the weekend).

I’ve just checked our help desk, and **can’t find any recent emails from you** — the last emails we received from you were in August and September of 2023.

Perhaps the email got lost or blocked. Can you try sending your support request again? [support@realmacsoftware.com](mailto:support@realmacsoftware.com) (or we can help you here on the forum, if that’s easier).

[Previous page](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180.md?page=3)

[Next page](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180.md?page=5)
