Skip to main content
Theme

Connectors

GoDaddy

The tool reads a GoDaddy Website Builder site (Websites + Marketing) from the published site, and copies it to an Insites v6 instance. It only reads. Nothing is ever written to GoDaddy, and no DNS record is ever changed. It copies the site's pages and design, menus, blog posts, forms, files and redirects. The online store, online appointments, contacts and email marketing stay on GoDaddy, and the plan lists each one.

Why there is no API key

GoDaddy's developer APIs cover domains, DNS, shopping and hosting. None of them reads a Website Builder site's pages, blog, forms, form messages, contacts or files, and GoDaddy documents no export of a whole site. So the tool reads the published site, as a visitor sees it: every page its sitemaps list, every file those pages load, and each form on them. What is not on the published site cannot be read, so it is either a file you add or a job on the To do list.

What you need

  1. In GoDaddy, open the site in Websites + Marketing and click Publish if it has unpublished changes. The tool copies what is published.
  2. In the tool, give the site's address as visitors open it: your own domain, such as https://www.example.com, or its .godaddysites.com address. The tool checks the page is a Website Builder page before reading anything.
  3. Optional: a GoDaddy Domains API key, so the cutover job names the domain's DNS records. Make a Production key at developer.godaddy.com/keys, in the GoDaddy account that holds the domain, and paste it as KEY:SECRET. The tool only reads the domain and its records with it. GoDaddy opens the Domains API to accounts that hold an active domain. Without a key the site moves the same, and the cutover job names the records in general terms.

A Domains API key is kept encrypted for as long as the migration needs it, and removed when you close the migration: how long a key is kept. Delete it at developer.godaddy.com afterwards.

What is copied

On GoDaddyOn Insites
PagesEvery page the site's sitemaps list, and the home page, read from the live site and copied to the same address, with its title, description and sharing tags.
Blog postsEach post is a page at its own address under /f/, with its images. On Insites they are pages, not a blog collection, so a new post is written as a page.
MenusThe header menu moves inside each page, so every page keeps the menu it had and its links point at the copied pages. A change to the menu is made on each page.
Design and filesEvery file the pages load from GoDaddy's file host (styles, scripts, fonts and images) is copied, and the pages name the copies. GoDaddy offers each image at many sizes; it is copied once, at its own size, and serves every size the page asks for. Files the pages' scripts fetch as they run are found by loading each page in a browser, at a desktop width and a phone width, and copied as well.
Sitemap and robots.txtThe sitemap is the one Insites serves at /sitemap.xml, listing every page that was copied except the not-found page. The site's robots.txt is copied with its own rules and points to /sitemap.xml.
FormsEach form, such as the Contact Us form, is rebuilt in the Insites form builder where it was on the page, with its fields and the ones it required. See Forms below.
Past form messagesFrom a file you add, one a form. See Past form messages below.
RedirectsFound by asking the live site, and from a list you add. Each goes into Settings, Redirects on the new site. See Redirects below.

Forms

GoDaddy's form posts to GoDaddy through GoDaddy's own script, so it stops working once the site has moved. Each form is taken out of its page and the rebuilt form is drawn where it was, built the way the Insites form builder builds one: its table first, named after the form, then the form with its fields, then a workflow email to the site's owner and an autoresponder to the person who sent it. A field whose label ends in an asterisk was required on GoDaddy and is required on Insites; the email field is checked as an email address. The form asks for an hCaptcha, as GoDaddy's asked for a reCAPTCHA. GoDaddy does not say who its form emails go to, so the Forms step of Transform asks. A file upload field is named on the plan and left off the rebuilt form.

Past form messages

GoDaddy keeps what people sent through a form in its own inbox, and has no API or documented export for it. To bring them over, copy each form's messages into a spreadsheet: a heading row with the form's own field names (such as Name, Email and Message) and a Date column, then one row a message. Save it as CSV and add it on the Form submissions step of Transform, beside its form. Each column is matched to a field by its name, and a column that matches no field is named, never dropped silently. Once the messages are in, an owner can add the people who sent them to the CRM: Add past enquiries to the CRM.

Redirects

Website Builder has no redirect setting of its own, so the tool finds what it can from the outside: every old address the Internet Archive has seen on the site, and every link on its pages, is asked of the live site, and each one the site sends somewhere else becomes a redirect. A redirect nobody linked to and no archive saw cannot be found this way. If you know of others, from a site the GoDaddy one replaced or from a domain's forwarding, add them on the Redirects step as a list, one pair a line, such as /old-page /new-page 301 or /old-page, /new-page. A redirect in your list wins for the address it names.

What stays on GoDaddy

  • The online store. Products, orders and customers stay on GoDaddy, as decided for this connector. The plan counts the store's addresses. GoDaddy can export the products as CSV, which is its only documented store export.
  • Contacts and subscribers. GoDaddy publishes no API for a site's contacts, so the tool cannot read them. The To do list says how to copy them into the CRM. New enquiries through the rebuilt forms add a CRM contact as they arrive.
  • Email marketing. Campaigns and their history stay on GoDaddy.
  • Online appointments. The booking widget and its bookings stay on GoDaddy.
  • Member sign-in pages. The pages under /m/ belong to GoDaddy's store, and the new site has no customer sign-in.
  • Form email wording. Each rebuilt form has the form builder's own workflow email and autoresponder. Change their wording in the form builder.
  • Email, Microsoft 365 and other GoDaddy products. They are separate products. Ending the site's plan does not end them.

After the migration

The To do list in Launch is written for a GoDaddy site. Each job names what this site has.

  • Domains and DNS. Add the site's domain to the new instance in Insites Console. In GoDaddy, open the domain's DNS and replace the A and CNAME records that point it at the Website Builder site with the ones Console gives. Leave the email records as they are. A site on a .godaddysites.com address has no domain to move: give the new site a domain of your own.
  • Forms. Open each form in the form builder: check who its workflow email goes to, read its autoresponder and switch it on, and send a test from the copied page.
  • Contacts. Copy the site's contacts out of GoDaddy and import them into the CRM before the plan ends.
  • The store and appointments. Decide what happens to each before ending the plan.
  • Search engines. Submit /sitemap.xml in Google Search Console once DNS has moved.
  • The GoDaddy site. Keep it, and its plan, until the new site has run cleanly through the 14-day watch. Then close the migration, delete the Domains API key if you made one, and cancel the Websites + Marketing plan. A domain bought through GoDaddy stays registered.

If it does not connect

The tool saysWhat to do
That address is not a GoDaddy Website Builder siteGive the address of the published site, as visitors open it. A site built with GoDaddy's WordPress hosting is a WordPress site: use the WordPress connector.
GoDaddy did not accept this Domains API keyPaste the key and its secret together, as KEY:SECRET, from a Production key. Or leave the field empty: the site moves without it.
GoDaddy's Domains API is not open to this accountLeave the field empty. The site moves the same, and the cutover job names the records in general terms.