Avada fix
Avada Prebuilt Website Import Failed or Stuck? Reset and Retry
An Avada prebuilt website is a large delivery: pages, images, sliders, layouts, menus, widgets and a full set of Global Options, fetched from ThemeFusion's servers in one run. When the run stops partway and stays there, the server usually ran out of time or could not reach the files. The fix is to clear out what arrived and bring the rest in smaller loads.
What you are seeing
- The import progress stops and never completes
- Pages arrived but their images are missing or broken
- Menus list every item twice after a second attempt
- The result looks nothing like the demo: wrong colors, wrong header
- The Websites screen says the product must be registered first
Why it happens on Avada
Most common first.
- 1
The server's time limit ended the run
Importing means downloading a great many images and creating every page in one long process. Shared hosting commonly stops any PHP process after a fixed number of seconds. The import dies in the middle of the downloads and reports nothing.
- 2
The Import button pressed a second time
When an import stalls, the natural move is to press Import again. Avada then adds another copy of whatever arrived the first time: duplicate pages, doubled menu items, a second set of widgets. The site now looks worse than before, and the cause is the retry.
- 3
Only part of the demo was selected
The import dialog lists the plugins a demo depends on and lets you choose which kinds of content to bring in. Leave out the Global Options, labeled Theme Options in older versions, and the pages arrive wearing your old colors and header. Skip a slider or shop plugin and its sections arrive empty.
- 4
Avada is not registered on this site
Prebuilt websites are delivered only to a site with a valid purchase code on the Avada dashboard. A staging copy or a new domain may not carry the registration that the original site had. The import is refused before it starts.
- 5
The host cannot reach ThemeFusion's servers
The demo content is downloaded at the moment of import. A host firewall that blocks outgoing requests, or outdated connection software on the server, stops that download. The dialog waits on files that are not coming.
How to fix it, in order
Least invasive first. Stop at the step that fixes it.
- 1
Start from a backup or an empty staging site
A prebuilt website import can overwrite Global Options, widgets and the home page setting. Do not run one on a live site with real content unless you hold a backup you have tested. A fresh staging install is the safer place for this job.
- 2
Remove the partial import before retrying
On Avada, Websites, open the demo you imported and use its option to remove the content it added. On a brand-new site with nothing to lose, starting again from a clean WordPress install is quicker. Never import over leftovers.
- 3
Confirm registration and server limits
Check that Avada, Dashboard shows this site as registered. Then open Avada, Status and ask the host to raise any PHP time or memory limit shown in red. An import that died on a time limit will die on it again.
- 4
Install the plugins the demo asks for
Open the import dialog and install and activate every plugin it names before importing anything. The bundled premium ones are installed from Avada, Plugins / Add-ons.
- 5
Bring the demo in a few content types at a time
Instead of choosing All, tick a few content types per run: pages and posts, then images, then sliders, with Global Options and widgets last. Shorter runs finish inside the server's time limit, and when one fails you know which.
- 6
Set the home page and menus, then compare
After the last part, check Settings, Reading for the home page and Appearance, Menus for the menu locations. Press Reset Avada Caches on the Performance tab of Global Options and hold the result against the demo. Whatever is missing tells you which part to remove and import again.
Keep it from coming back
- Import onto a clean staging site and move the finished result to live
- Clear the red items on Avada, Status before importing, not after a stall
- Never press Import a second time without removing the first attempt
- Run the Performance Wizard afterward to switch off what the demo brought and you will not use
The permanent fix
A faster Next.js build, with a CMS made for your business
A stalled import is a server limit, not a verdict on the site. It is worth pausing on what the import is for, though: a design made for a fictional business, which you then spend weeks bending toward your own. If the plan is a site shaped around your services and your customers, a Next.js build with a custom CMS starts from those, and there is nothing to import, trim or keep in step afterward.
| On Avada today | On Next.js with a custom CMS | |
|---|---|---|
| What you keep updated | WordPress, the theme, its builder and every bundled plugin, all in step | Nothing on a schedule. There is no theme or plugin stack to fall out of step |
| How a page is served | Built from the database on each visit, through the theme and its builder | Built ahead of time and served as finished files from servers near the visitor |
| How you edit it | A general-purpose builder with every option the theme ships | A CMS built around what your business actually changes: services, prices, photos, posts |
| What can break it | An update to any one of those parts, or a license that lapses | A change someone makes on purpose, tested before it goes live |
Your content, your addresses and your rankings come with you: every page is moved, every old address is redirected, and you get a login to an editor that only shows what you need. A repair is still the right call for many sites, and we will say so when it is.
Want this fixed on your Avada site?
Tell us what you are seeing. We look at the site, tell you plainly what is wrong and what it takes, and quote a fixed price before any work starts.
Which of these sounds like you? (pick any)
Frequently asked
It does not delete them, but it adds its own content beside yours, can replace Global Options and widgets, and may change which page is the home page. On a site with real content, that is a redesign. If you want one layout from a demo, the builder's library can bring in a single prebuilt page instead.
The import ran more than once without the first attempt being removed. Each run adds its menu items again. Remove the imported content from the Websites screen, delete any leftover menus on the Appearance, Menus screen and import once more in parts.
Yes. Prebuilt websites are part of what registration unlocks, along with automatic updates and the bundled plugins. If you are working on a staging copy, check its registration panel as well, because it may not carry the live site's.
It varies with the size of the demo and the speed of the host, from a few minutes to much longer. A better test than the clock is the Media Library: if no new images have appeared for several minutes, the run has stopped and waiting will not restart it.
Keep reading
- ServiceFixing Broken WebsitesSite down, hacked, or falling apart? We diagnose it fast, fix what's broken, and tell you straight how to keep it from happening again.
- ServiceBest WordPress DesignA WordPress site that looks the part and does the work. Custom design, fast pages, and a layout built to turn visitors into customers.
- ServiceWebsite Hosting & Maintenance PlansThe watching after launch: managed hosting, tested updates, backups that restore, security and uptime monitoring, and small edits done within a day, month to month.