Migrations: URL Redirects and how they work

Jeana Hollingsworth

Because the Convio URL structure does not match the GetActive URL structure, the URLs cannot be setup in the same manner and thus must be setup as a URL redirect during migration, e.g

• GA URL: http://www.nifjoin.org/justice/join.html
• Convio URL: http://www.nifjoin.org/site/PageServer?pagename=register

When migrating this could cause problems accessing those older links.  For example, constituents may still have older emails that have links to the old GA pages.  Also, if the client has links on other organization’s websites, those links may be GA link.

What we do to work around this problem is we create a list of URL redirects.  The URL redirects is basically a file that says “if the constituent is trying to go to URL x, redirect them to URL y”.  This way, if the older URLs are used, the constituent is directed to one of the new Convio pages.

URL redirects once the GA platform is retired

The URL redirects will not be available forever.  They will be active for at least 90 days, perhaps longer.  However, once the GA platform is retired, all redirects will also be gone.  Because of this, client should endeavor to make every effort to update the links not only in their own content but also links found elsewhere.  Once the URL redirects are turned off, any URLs that once relied on the URL redirects will not work.

URL Redirects and TCL files

In most scenarios, clients do not use the exact same URL for their COM/CRM content in both GA and Convio.  If the exact same URL is used for GA COM/CRM and Convio COM/CRM, it can cause one slight problem.  Links with URLs that have a TCL file will not redirect.  TCL files are not understood by Convio and thus the redirects fail to redirect constituents to the desired Convio page.  If the client has any links with TCL files, it is recommended that the client update any existing links that use TCL files.

For more information about subdomains, domains, and URLs, see this document.