How to deliver the Completed Theme?

Migrating a site from development to the client’s live server can be handled in various ways. We have an article at https://elementor.com/blog/site-migration/ that can help clarify one good way to go about this. Site Migration is a rather broad topic, which isn’t really Elementor specific, nor even WordPress specific, but WordPress can make it easier with the use of plugins, as mentioned in the article I linked to.

Yes, a site migration always involves both files and a database. Yes, a database would contain test data as well, unless you clean out that data. Clearing out that data shouldn’t be all that painful but if you anticipate a lot of it, you may want to be proactive and keep notes of what needs cleaning before making the site live.

No, you would never want to develop a site directly on the client’s live domain. You would either develop locally, perhaps using something like Local by Flywheel (my favorite) or WAMP, MAMP, or XAMPP. Or you would develop the new site on a subdomain or test domain, and then move it to the live domain when ready.

Hope that helps.

Thanks @cavalierlife for the reply.

I clearly understand and know how to actually migrate WordPress sites, my question was specifically for the WebSites [templates] developed using Elementor. If I got it right all the templates are being stored in the back end database and there are no template files as is the case in traditional theme development.

All you have to do is Package all your theme files in a zip file and share with the client or help him with the install by uploading those files to his server/domain and activate the theme [usually a child theme]. I was am still wondering if there is an easier way of delivering theme files [build using Elementor] to the clients?

I was expecting something like an export of the Elementor related stuff to [may be] a JSON file which then can be imported on the Clients Domain.

Thanks Again!

Templates can be exported to JSON files, yes. But that’s only going to give them the ability to import the templates which they can then use to create new pages, etc. That’s not going to give them an entirely built site.

Templates are not the same things as themes. In essence, you can’t just export a “skin” and then import it into a client’s existing site, flip a switch, and have all their current content magically use the new skin.

Well, actually, that’s not even totally true either. You could just create Single Page, Single Post, and Archive templates using Pro’s Theme Builder, export those as JSON files, and import them to apply a template skin to existing posts, pages, and archives. But if you’ve used Elementor to design any actual content, that won’t get transferred in that import.

So, I guess it depends on specifically what you are doing for the client. I assumed you were creating an entire site, in which case, you’d migrate as usual. Now I’m not quite sure what you will be doing for them.

Thank for the quick response @cavalierlife

I am just about the learning Elementor, and want to know these things in advance actually working on a clients site. I do understand the difference between templates and pages. I am glad to know that at least we can export templates as JSON files and then import them on the clients site.

Please let me know if I am mistaken, what if I create a page [using elementor] and then save it as a template. What about exporting it and then importing on another site, would it carry all the bells and whistles of the Page or ???

Yes, you can save an entire page as a template, export it, and import it into another site, and it should carry all the bells and whistles with it, with the exception of custom fonts. They are not imported through this process, so they would need to be added manually.

So, there’s a work around @cavalierlife

Thank you so much for your help!