Test environment was a LAMP box, while we were waiting for the windows box to get setup. Well that's done, and now I find myself having to migrate a rather large number of nodes (across 4 sites) from mySQL to msSQL (which means backup and migrate is out).
I've looked at the Node Export module, but seeing as I have 10+ pages of nodes in some cases, makes this a very time consuming task.
I made several attempts with VBO, but that yielded nothing but errors (was in their issue que, this error seemed to be common if you want to batch anything above 5 nodes).
Features - Says it should do the job. Great. However I wasn't able to find any "good" documentation about how to actually get it to work. I've installed all related modules, created a feature (I think), but now what? Does anyone happen to know of a tutorial using this?
Drush - Haven't used it at all, attempted to install once and that didn't go well (I'm not very "command line" friendly/savvy), so that's not an option.
Which leaves me with Exporting 50+ pages of nodes... Unless anyone has any other suggestions?
All these sites were brought over from WordPress, so I guess I could also re-import with the wordpress migrate module... I should've taken notes on that...
Eh at least I can easily move the themes, and clean URL's didn't give me any issues :) Yay for the small victories!
Comments
This module may help you
This module may help you http://drupal.org/project/node_export
-Imran
---
Helps to read the entire post before responding!
=-=
vbo wouldn't aid with data migration
features wouldn't aid with data migration
drush wouldn't aid with migration
modules I'd investigate:
http://drupal.org/project/migrate_d2d or http://drupal.org/project/feeds
---
Unfortunately I don't see a mention of exporting with Feeds. I still need to get the nodes out of my site somehow.
As for Migrate_d2d - Looks like the 2 sites have to be able to "talk", which isn't possible as one is a local copy on my mac and the new one is a windows machine that I have to remote into from a separate computer.
Which still leaves me with no great options :) I guess this situation doesn't arise often!
=-=
documentation will aid in your understanding. One can feed the data from one site to another as a method of migration.
---
Which I'm guessing requires the sites be able to "talk", which isn't possible.
=-=
surely, it's possible, but if you aren't willing to take the steps to have the sites "talk"; and you won't move them to the same machine to deal with the task, then you're severely limiting your options. your only options as I see it are to forge ahead and use node export or to export the necessary tables manually from the DB (I've no advice on that task).
---
Is there a way to get a live windows server to talk to a local dev server?
It has nothing to do with WON'T move, unless there's something I'm unaware of, I can't move a site with a mySQL site onto a server with msSQL.
=-=
Why has node export been eliminated as time consuming? based on the project page you can export content (I don't see where it's fixed to one node at a time) into a csv file, xml file among other methods, which can then be imported with the feeds.module without the sites having to know about the existence of the other as you'd be dealing with a file exported on one machine and imported into the other.
---
It's not fixed to one node, it's fixed to all the nodes on one page (roughly 50 nodes). I've checked, and of the 3 sites I need to export each has roughly 15 pages of nodes (the one has just over 20). I never said it wasn't a doable solution, I was just hoping there was an option that might be a bit swifter.
Going to try dumping the data a few different ways and see if I can find a "nice" way to directly import into the new db.
=-=
perhaps momentarily hacking the module responsible (node.module I believe) for generating the administer -> content page to increase the amount of content listed ? There should be a page query dealing with the amount of content per page.
---
Now that's a good idea...
Normally I'm against all hacking of "core" modules, but in this case... Eh it's a local dev copy that I've backed up, what's the worst that could happen?
Thanks!
---
Worked like a charm! Thanks!
=-=
I don't normally condone hacking core either, but if it helps and its reversible ....
glad it worked out.
---
Found an interesting module to try (dbtng migrator), and an issue from a ways back that could be useful.
Still open to any other suggestions!