Content Migration

We will migrate content from your current website as-is to your new Govstack CMS. It takes our content migration team approximately 20-30 minutes per page to migrate the content.

Content migration includes:

• Migration of the set number of pages stated within your contract
• All pages must appear in the sitemap/navigation of the current live site 
• All images that appear in page content (the source image resolution may not be appropriate for the associated image area in the new website. As a result, it may appear stretched or low-quality. You will be responsible for sourcing new images)
• All documents that appear in page content
• Embedded videos
• Relinking between pages, documents and images
• Any links with a "mailto:" email address 

If you're migrating content from an i:Create website, we'll also include:

• All documents saved in file manager
• Form Builder forms and all historical response data 
• Events and Council Calendars including all events, files and users
• Up to 500 contacts within the Contacts Directory

There are some exclusions from the content migration process. You should budget approximately 10 minutes per page to clean up your content following content migration. You'll be responsible for: 

• Landing pages, microsite home pages and pages with special layouts (these can be included at an additional cost, however, the pages may not look the same in Govstack due to CMS differences)
• Downloading and archiving any unpublished content or orphan pages that might be in the back-end of the current CMS and not linked in the navigation
• Banner images (you'll need to replace the image size to fit the new Govstack banner design)
• Fixing broken links, spelling mistakes or accessibility issues that may be in your current website
• Custom CSS, HTML or JavaScript that is on the current website 
• News posts (unless added to scope)
• Any files over 150 MB cannot be uploaded to Govstack (you'll need to resize and upload any files larger than 150 MB)
• Some third-party integrations may not be available in Govstack (these will be removed from the content and noted)
• Links to orphan pages will be kept the same (linking to previous site) and will break when the new site goes live (you'll need to create the orphan page in Govstack and relink before go-live)
• Orphan pages and external links can't be formatted into a Subpage Listing in Govstack

If you're migrating content from i:Create, the following is not included:

• Documents stored in the i:Create Bylaw module and Document Manager module
• Links to individual contacts in the Contacts Directory found within page content will break and you will need to relink to the main Contacts Directory page or create "mailto:" links
• We can't assign per page contacts in Govstack (there is a workaround where you can create a reusable Pod for a contact using the Text/Image component that you can add to individual pages in addition to the general Contact Us. This will not be done as part of the content migration)
• Page subscriptions are not available in Govstack