How to import content from a temporary site to a new domain
Moving from a temporary domain to a permanent home is more than copying a few pages across. A reliable content migration moves the underlying HTML, images, documents, metadata, internal links, forms and associated records while keeping the user journey intact. It also manages old URLs, search signals and technical details such as certificates and redirects. The temporary site might be an old public website, a private staging build or a parked page. Each requires a different starting point, but the same objective: publish the right content on the new domain without broken paths, duplicate pages or lost visibility.
If the current domain is a parked GoDaddy page, its welcome message, hosting attribution, copyright notice and privacy link do not form a transferable website. There may still be useful files in a CMS, media library or hosting account, so inspect the actual account rather than judging it by the front page. Do not scrape material you have no permission to reuse, and never treat hosting-provider attribution as content ownership. If the source genuinely contains only a placeholder, the migration begins with creating the new site's substantive pages rather than copying an empty shell.
A safe launch starts with a complete inventory, a restorable backup and a temporary destination where staff can test the result. Record where each URL will live on the new domain, then check that page titles, descriptions, canonical tags, image alternatives and calls to action still make sense. Keep tracking operational from day one: retain analytics, preserve Search Console and Bing Webmaster Tools access, and log every old-to-new redirect. This prevents a technically successful upload from becoming a confusing or invisible launch.
| Migration approach | Best fit | Expected downtime | Search and URL handling | Main risk |
|---|---|---|---|---|
| CMS export and import | Sites built with WordPress, Joomla or similar systems | Minutes to several hours | Usually preserves URLs, metadata and structured content | Hidden database relationships or missed plugins |
| Direct file transfer | Static sites and simple brochure pages | Minutes to an hour | Requires manual URL and redirect mapping | Incorrect paths, missing files or encoding errors |
| Platform-to-platform migration | Moving between hosted builders or website services | Several hours | Depends on available export tools | Layout, code and third-party features may change |
| Manual rebuild | Outdated, customised or badly structured sites | Days to weeks | Needs a complete URL and content plan | Scope changes and inconsistent metadata |
Audit the source and protect ownership
Begin with a URL-level audit rather than a visual review. Crawl the temporary site and record every indexable page, blog post, image, video, downloadable document, form, email address and embedded application. Note the current URL, intended destination, owner, approval status and whether the asset contains personal information. Check the sitemap, robots.txt file, analytics data and server logs as supporting evidence. If the public domain is parked, look directly inside the hosting account, CMS and cloud storage for content that may not be linked from the front page.
Confirm that the organisation has the right to move every item. A copyright notice on a placeholder page does not grant permission to copy third-party text, photography, logos, reviews or promotional material. Australian websites may also need to assess obligations under the Privacy Act 1988, including the Australian Privacy Principles, when transferring customer or subscriber information. Commercial email should comply with the Spam Act 2003, and online sales or service terms should be checked against the Australian Consumer Law. Legal, privacy and marketing owners should approve the content list before migration begins.
Choose a domain that is easy to say, spell and remember, then document it consistently across hosting, email and business records. If the address is still being selected, domain naming guidance can help evaluate clarity and recall. Australian organisations may consider a .com.au domain or an eligible .au direct domain, checking current auDA requirements and registrar pricing. Once selected, use the same hostname format everywhere and decide whether www and the bare domain will redirect to one preferred version.
Build the URL map and staging copy
Create a migration sheet with three columns: the existing URL, the corresponding new URL and the action required. Preserve established directories, content types and meaningful page slugs wherever possible. For example, an existing /services/bookings/ path can usually move to /services/bookings/ on the new domain, while a complicated legacy URL should receive a clean replacement. Avoid changing paths unnecessarily, because every alteration introduces another redirect, another opportunity for error and another potential loss of accumulated search visibility.
Build the destination as a private staging environment while the team checks the content. Password protection or access restrictions are preferable to leaving unfinished pages publicly indexed. Test navigation, internal links, images, downloadable files, contact forms, appointment tools, checkout processes and embedded media. Check page titles, meta descriptions, heading order, image alternative text, structured data and social-sharing previews on a real phone as well as a desktop. A page can pass a link checker and still offer a poor experience on a narrow mobile screen.
Keep excluded material out of the copy. A crawler might find an unrelated commercial page, including live baccarat promotions, and record it in the audit, but indexing does not make it part of the temporary site. Mark such pages as excluded rather than importing them because they appeared in search results. The same rule applies to material supplied by former staff, agencies or third-party publishers unless ownership and permission are documented.
Transfer files, DNS and email
Take a restorable export before touching the source. Download the CMS database, uploaded media, configuration files, redirects, form entries and any third-party content that cannot be recreated. Keep the original export unchanged, then make a working copy for migration. Preserve file names, folder structure and character encoding where practical, because damaged accents, broken filename spaces and altered image paths can affect both accessibility and search indexing. Test the upload against the staging site before changing any nameserver or domain record.
Prepare DNS in advance. Lower the existing TTL values on relevant records at least 24 to 48 hours beforehand, then confirm the destination's A, AAAA or CNAME records, nameservers and SSL certificate. Email is a separate migration path: review MX records, SPF, DKIM and DMARC configuration rather than assuming website hosting will carry email across. Schedule the switch around local business activity and account for Australian time zones. Sydney and Melbourne observe daylight-saving changes, while Brisbane and Perth do not, so a single overnight window can have different operational effects across the country.
Redirect equivalent old pages to their new locations with a permanent 301 redirect. Each redirect should lead directly to the closest relevant page, preserve useful campaign parameters and avoid chains, loops or redirects to the home page. When no equivalent exists, return a genuine 404 response rather than concealing missing content. Keep the old domain and hosting active for at least 12 months where practical, because visitors may retain bookmarks, printed links or messages that predate the launch. Maintain a single approved redirect map so changes do not create conflicting rules.
Preserve search signals and useful links
Update the absolute canonical URL, XML sitemap, robots directives and internal links to reference the new domain. Preserve each page's intent rather than rewriting every title simply because the address changed. Verify that the migration platform has generated the same metadata, headings and structured data visible to crawlers. Add the new domain as a property in Google Search Console and Bing Webmaster Tools, submit the sitemap and run a URL inspection on important templates. These services reveal redirect errors, excluded pages and indexing changes that ordinary analytics may miss.
Review the old site's backlink profile before deciding which relationships to preserve. Relevant links from Australian industry bodies, local councils, chambers of commerce, suppliers and reputable publications usually deserve attention. Update citations where possible, particularly those attached to local search profiles such as Google Business Profile. If the business serves physical customers, make sure its address, phone number, opening hours and service areas remain consistent across Australian directories. Mobile access matters here: commuters in Sydney, Melbourne, Brisbane and Perth may encounter a changed page through search or social media long before they return to a laptop.
Use analytics to compare impressions, organic sessions, landing pages, conversions and search queries before and after the switch. Keep existing campaign tagging intact and test that forms send the right data to email, CRM or automation systems. Check page speed, image compression, browser errors and server response codes from several locations. Search visibility can fluctuate briefly while crawlers process the redirects, so judge the launch over several weeks rather than a few hours. Preserve historical data rather than resetting counters, which makes the before-and-after comparison much more useful.
Launch, monitor and complete the handoff
Use a written launch runbook with clear ownership and a rollback point. Freeze last-minute structural edits, run a final backup, export the latest database and verify that staging still matches production. After changing DNS, confirm the live domain, preferred hostname, HTTPS certificate, redirects, sitemap and key conversion paths from an external network. Test a real contact or booking submission and receive confirmation at the destination mailbox. Keep the old site available until these checks pass, and assign one person to coordinate DNS, hosting, email, analytics and website decisions.
Monitor the launch intensively. Review uptime, server logs, 404 reports, redirect chains, form deliveries and contact-form spam at frequent intervals during the first 48 to 72 hours. Compare traffic and conversion data with the previous period, and keep the website team, IT provider and communications contact available during normal Australian business hours. Correct broken destinations promptly rather than waiting for the next redesign. Update documentation, bookmarks and staff processes once the new domain is stable, while retaining the migration map and backups for future reference.
Open the hosting account today, list every asset you are permitted to transfer, and load the first verified batch into a protected staging environment before making any DNS change.