# An idea to make the transition from Classic to Elements easier

**URL:** <https://forums.realmacsoftware.com/t/an-idea-to-make-the-transition-from-classic-to-elements-easier/49951>\
**Category:** Elements\
**Created:** [August 19, 2025, 3:55pm UTC](https://forums.realmacsoftware.com/t/an-idea-to-make-the-transition-from-classic-to-elements-easier/49951 "2025-08-19T15:55:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ulrich](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ulrich/32/29764_2.png) [@Ulrich](https://forums.realmacsoftware.com/u/Ulrich)\
**Post date:** [August 19, 2025, 3:55pm UTC](https://forums.realmacsoftware.com/t/an-idea-to-make-the-transition-from-classic-to-elements-easier/49951/1 "2025-08-19T15:55:34Z")

</div>

Many people want to switch from Classic to Elements. Being able to import resources would be a huge help. Unfortunately, direct drag-and-drop isn’t possible.

Wouldn’t “Import Resources from Classic Project” be awesome? Perhaps you could also import the page structure and naming. Many parameters like path, description, browser title, menu description, keywords, etc. are the same.

Sure, you can’t import the page content, and I wouldn’t even try. But the structure and the tedious parameters and resources would be a huge help.

---

<div class="post-metadata">

**Author:** ![MichaelDroste](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/michaeldroste/32/37212_2.png) [@MichaelDroste](https://forums.realmacsoftware.com/u/MichaelDroste)\
**Post date:** [August 19, 2025, 4:26pm UTC](https://forums.realmacsoftware.com/t/an-idea-to-make-the-transition-from-classic-to-elements-easier/49951/2 "2025-08-19T16:26:59Z")

</div>

I just leave classic open and elements open - and copy paste needed content from classic into elements

I also like to restructure my content folders going into elements for easier access:

Graphics, Audio, MIDI, SVG, PDFs etc

---

<div class="post-metadata">

**Author:** ![DaveMac](https://avatars.discourse-cdn.com/v4/letter/d/fbc32d/32.png) [@DaveMac](https://forums.realmacsoftware.com/u/DaveMac)\
**Post date:** [August 19, 2025, 5:14pm UTC](https://forums.realmacsoftware.com/t/an-idea-to-make-the-transition-from-classic-to-elements-easier/49951/3 "2025-08-19T17:14:43Z")

</div>

Good idea.

Blocs Plus offers a [basic extractor tool](https://academy.blocsapp.com/video/how-to-import-images-from-a-website/) for live sites that extracts images, typography and color from a live website for re-designs.

Maybe something similar or **even more robust** (for more inclusive migration) could eventually make its way into Elements. Unless extracting items from within a referenced RW file could also be doable. Though pulling from a live site allows migration from any tool or site.

---

<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 19, 2025, 6:47pm UTC](https://forums.realmacsoftware.com/t/an-idea-to-make-the-transition-from-classic-to-elements-easier/49951/4 "2025-08-19T18:47:06Z")

</div>

I think you will find this impossible IMO as they are written in two different languages, also ELEMENTS strips out loads of code and is smaller in file size and quicker too. @dan will im sure give you the full details
