# 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:** 3

<div class="post-metadata">

**Author:** ![Flash](https://avatars.discourse-cdn.com/v4/letter/f/f475e1/32.png) [@Flash](https://forums.realmacsoftware.com/u/Flash)\
**Post date:** [August 26, 2025, 5:45pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/41 "2025-08-26T17:45:39Z")

</div>

> [@Pegasus](#):
>
> I do have concerns that fixing the especially annoying bugs (and there are still quite a few) might end up being pushed far into the future…
> 
> Right now, with both the CMS and this tool, it just feels like there are too many “work in progress” projects at once.

This

---

<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 26, 2025, 5:54pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/42 "2025-08-26T17:54:32Z")

</div>

> [@WeaverPixel](#):
>
> that would be extremely helpfull to rebuild my website [Https://weaverpixel.com](Https://weaverpixel.com). It is still made with Classic and Foundry 3.

Awesome, I’m looking forward to seeing your new site built with Elements 🤩

---

<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 26, 2025, 5:56pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/43 "2025-08-26T17:56:03Z")

</div>

> [@ajenks](#):
>
> Only downside for me is most of my RW sites use the SEO Helper stack, so all that info wouldn’t be migrated.

I think we already have most things covered, but what are the exact SEO features you need that are not available in Elements?

---

<div class="post-metadata">

**Author:** ![sjallyn](https://avatars.discourse-cdn.com/v4/letter/s/aca169/32.png) [@sjallyn](https://forums.realmacsoftware.com/u/sjallyn)\
**Post date:** [August 26, 2025, 6:42pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/44 "2025-08-26T18:42:10Z")

</div>

when you have a complete conversion kit in Elements so that I can bring my entire site over, content and everything, and it will look almost like it did, then I would consider switching, until then, I can’t it’s too much 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 26, 2025, 6:42pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/45 "2025-08-26T18:42:13Z")

</div>

> [@Pegasus](#):
>
> The problem is, at least for me, it just comes too late.

Agreed, however there seems to be a fair few Classic users who have yet to make the move and if we want Elements to be a success we need to get them moved across!

> [@Pegasus](#):
>
> For me, it was better to just build a completely new site from scratch.

Yup, totally understand that, it’s what I’m doing with the Realmac site, it’s a chance for a fresh start!

> [@Pegasus](#):
>
> Right now, with both the CMS and this tool, it just feels like there are too many “work in progress” projects at once. But given how much attention and enthusiasm this tool is getting, I guess we’ll just have to be patient—bug fixes and CMS improvements may take a bit longer.

Don’t worry about that, the CMS is still progressing very nicely, and we have more big fixes dropping soon. 😉 We’re a team so we can juggle multiple things at once. So long as we make progress everyday, everything keeps getting better.

New build coming later this week!

---

<div class="post-metadata">

**Author:** ![luckylindy](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@luckylindy](https://forums.realmacsoftware.com/u/luckylindy)\
**Post date:** [August 26, 2025, 7:24pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/46 "2025-08-26T19:24:07Z")

</div>

This looks promising, Dan. I have a site I spent a lot of years ‘perfecting’. And while doing it in Elements from scratch is definitely on my list, it is daunting from a ‘can Elements do this’ perspective. If I could import it and see how much travels over and how much gets left at the station, I’d be able to offer a better opinion here on how much I like what you have and what more it needs.

I note that you didn’t show any of the other imported pages; maybe that would have helped me form an opinion, in lieu of having a build with an import function. I think this is definitely worth the effort.

Maybe it’s time for some version 1 beta builds (a beta channel?) that we can try out ourselves before you bake them into an official v.1x.x releases? This Import function would be a great candidate for such a beta. I think most people would want this but need to have experience with it in order to provide input for you to make it better

---

<div class="post-metadata">

**Author:** ![ajenks](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ajenks/32/34693_2.png) [@ajenks](https://forums.realmacsoftware.com/u/ajenks)\
**Post date:** [August 26, 2025, 8:16pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/47 "2025-08-26T20:16:44Z")

</div>

It’s not that you guys don’t have the SEO features, its that I can’t migrate all the SEO info from RW becuase its inside a stack.

---

<div class="post-metadata">

**Author:** ![Pegasus](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/pegasus/32/25035_2.png) [@Pegasus](https://forums.realmacsoftware.com/u/Pegasus)\
**Post date:** [August 26, 2025, 8:45pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/48 "2025-08-26T20:45:08Z")

</div>

I completely understand that you want to get as many RW Classic users excited about Elements as possible and bring them onto the new platform.

That’s totally understandable, and judging by all the comments in this thread and the likes here and on the YouTube video, there really does seem to be huge demand. So you should definitely focus on that!

I know you’re a team. That’s actually one of THE reasons I decided to go with Elements and Realmac…

My concern is just that too many new projects at once might be too much, even for your team. You know the community… they’re always hungry ^^ … and expectations are high!

I know you and the Realmac team are doing your best—so honestly, it’s all good.

---

<div class="post-metadata">

**Author:** ![kitmos](https://avatars.discourse-cdn.com/v4/letter/k/4491bb/32.png) [@kitmos](https://forums.realmacsoftware.com/u/kitmos)\
**Post date:** [August 26, 2025, 8:58pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/49 "2025-08-26T20:58:38Z")

</div>

Agreed. I’d like to see many more projects avail. Either free or a reasonable price.

---

<div class="post-metadata">

**Author:** ![TomM](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/tomm/32/265_2.png) [@TomM](https://forums.realmacsoftware.com/u/TomM)\
**Post date:** [August 26, 2025, 10:15pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/50 "2025-08-26T22:15:19Z")

</div>

What happens when your Classic project has 40 photo album pages that require full frame, horizontal and vertical thumbnails on the same page?

---

<div class="post-metadata">

**Author:** ![davelord](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/davelord/32/5280_2.png) [@davelord](https://forums.realmacsoftware.com/u/davelord)\
**Post date:** [August 26, 2025, 10:17pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/51 "2025-08-26T22:17:14Z")

</div>

This is the “deal-breaker” feature I think a lot of Classic users have been waiting for.  
At the risk of creating even more “works in progress”, how difficult would it be to extend this feature to be able to import the architecture from other existing websites? I am thinking it would be awesome if we can just import a new client’s current site as the starting point in the process? This would save a HUGE amount of time duplicating URLs, and would ensure that they all match.

---

<div class="post-metadata">

**Author:** ![gudnuz](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/gudnuz/32/29127_2.png) [@gudnuz](https://forums.realmacsoftware.com/u/gudnuz)\
**Post date:** [August 26, 2025, 10:22pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/52 "2025-08-26T22:22:10Z")

</div>

Sounds good to me. I am currently redesigning one site, and have a couple others that could be done. I like not having to rename pages, etc., and re-accumulate the resources. I use a lot of resources on one site in particular, and finding their location…. well, I would use the import for whatever amount comes over.

---

<div class="post-metadata">

**Author:** ![myildi](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/myildi/32/30687_2.png) [@myildi](https://forums.realmacsoftware.com/u/myildi)\
**Post date:** [August 27, 2025, 12:01am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/53 "2025-08-27T00:01:10Z")

</div>

Thanks a lot! That, and the ability to import at least straightforward HTML pages and Stacks pages built by the default Stacks, would be very useful.

I am an academic and I have a rather extensive pedagogical website. I dont really have time to rebuild it from scratch. This is why I am sticking to Classic for now and I hope that you will not abandon it before building a content import module in Elements.

Thank you.

---

<div class="post-metadata">

**Author:** ![jazzvibe](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/jazzvibe/32/13769_2.png) [@jazzvibe](https://forums.realmacsoftware.com/u/jazzvibe)\
**Post date:** [August 27, 2025, 12:11am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/54 "2025-08-27T00:11:52Z")

</div>

The ability to import my site (or even site structure) from Classic would help me a lot!

---

<div class="post-metadata">

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

</div>

Not dead yet, cant screw it up then watch traffic die until AI becomes mainstream and for those with muscle memory leaning towards Google.

---

<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 27, 2025, 9:51am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/56 "2025-08-27T09:51:47Z")

</div>

I didn’t say it was dead, I was saying that its changing and our set ups need to change so old SEO requirements need rethinking.

---

<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, 10:56am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/57 "2025-08-27T10:56:48Z")

</div>

> [@myildi](#):
>
> Thanks a lot! That, and the ability to import at least straightforward HTML pages and Stacks pages built by the default Stacks, would be very useful.

Yes, we’re working on it now 😉

While Elements will import resources and _some_ content from Stacks pages, it won’t mimic the design, so you’d still need to do the work to get it looking how you want.

Still, it will be a real time-saver for everyone moving to Elements!

---

<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:20am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/58 "2025-08-27T11:20:27Z")

</div>

Hi Dan, I purchased and been playing around with Elements for a few weeks now trying to rebuild a fairly basic website and I am gradually getting there. 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. I also want to rebuild my other much bigger site. Being able to import as much of the existing Classic structure (and content?) to Elements as possible would save me heaps of time and effort. But I can’t go live until I get that private members page.

---

<div class="post-metadata">

**Author:** ![archerjohn](https://avatars.discourse-cdn.com/v4/letter/a/7ba0ec/32.png) [@archerjohn](https://forums.realmacsoftware.com/u/archerjohn)\
**Post date:** [August 27, 2025, 11:46am UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/59 "2025-08-27T11:46:33Z")

</div>

Thanks for the video. The ability to import resources is likely to be the major factor in my decision to migrate to Elements and will save me a lot of time.

---

<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:33pm UTC](https://forums.realmacsoftware.com/t/dev-diary-96-import-classic-projects-into-elements/50180/60 "2025-08-27T12:33:19Z")

</div>

Awesome 🎉 We’ll have a build out later this week that will import all resources from a project, including those stored in a Stacks page!

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

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