Data migration

Hello Sébastien,

FUP can handle this in two ways:
- if you don't have many redirects of this type, you can use the simple rewrite system by pairing your previous urls to your new ones:


- If you have many urls that need being rewritten, you can insert them in the url store through a sql script. What's interesting is that if you activated the 301 redirect, these urls will then be redirected to the rewritten values by FUP; for example http://website/page?id=123 will be matched to http://website/default.aspx?tabid=321 and then redirected to http://website/pagename (or whatever url your rule resolves to)

Best regards,
Samy

Hello Samy

Thanks for your answer.

I just tried your solution:
- I have added an entry into the Simple Rewrites tab with the legacy url and the new one. When doing this a new entry has been added into the FupUrlMapping table with
RealUrl = the legacy url
FriendlyUrl = the new url (which is in raw format (something like http://mysite/Default.aspx?tabId=1234))
- There is an entry in the mapping that converts this raw url (http://mysite/Default.aspx?tabId=1234) into a friendly url (for example http://mysite/Users.aspx
- I have activated the 301 redirects

If have correctly understood, when trying to browse the legacy url, I should first have a 301 redirect to its corresponding new url (in raw format) and then a second 301 redirect to the friendly url of this page: when calling the legacy url I receive a 404 error instead.
I don't know if this was clear for you but the legacy url does not exist on the DNN web site (so a 404 error seems logical, but I expected the FUP module to take the request and convert it to the corresponding new url); maybe I have missed something when setting up the module. Please let me know.

We have approximately 400 legacy urls we want to maintain on the new site; this means that we will have to enter these urls in the mapping table through a SQL script; but when doing so, if we empty the url store through the admin interface all these entries will be removed (which is different from setting these entries by hand because even if emptying the url store, these mappings are kept); is there another way for inserting a huge number of rewrites into the mapping table without loosing them when emptying the url store ?

Thanks

Sébastien

Hello Sebastien,

I'm going to look deeper into the 404 problem and will let you know how it must be configured exactly.

Regarding the url store, indeed emptying it would necessitate reinserting the lines. However emptying the url store is not recommended during day-to-day operations of FUP, since rebuilding it will depend on browsing the site in order to force DNN to display possible urls. If this point is very important, it is indeed better to use simple rewrites.

Best regards,

Samy

Hello Sébastien,

I looked into the problem as promised. I made a mistake when explaining in what order the 301 redirection would work, so i'm going to try and clarify:
When you set up a rule in FUP, you will match raw urls to rewritten ones in a batch. All raw urls will be rewritten following this rule if applicable.
Simple pairs actually allow you to sidestep this set up rewriting. all rewritten urls are compared depending on their raw url

301 redirect will therefore happen when two rewritten urls match the same raw url. The latest rewritten url will become the reference and previous urls matching the same raw url will redirect to it with a 301.
So what i told you regarding the simple rewrite is incorrect. If you want to benefit from the 301, you must redirect your previous urls to the raw url you want ot point to.

Sorry about the mistake; i hope this will help you in your data migration.

Best regards,
Samy