You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

OTAC Taleo to Recruiting Cloud ORC Data Conversion

in Recruiting, Opportunity Marketplace

Summary:

We are reviewing our conversion strategy with users and proposed converting only what we need (open requisitions/candidates) and archiving the rest. Our users are vehemently opposed to this approach and want all data converted.

I would love to hear from other customers on what approach was taken for conversion and lessons learned - what worked or didn't work.

Content (required):

Our users feel strongly that all candidate data (including attachments) along with all requisition data should be converted from Taleo to ORC. I think this will be a huge undertaking to extract, map all of the data, load and validate. Further, some of the data feels like clutter - incomplete candidate submissions/profiles, rejected candidates we would never reach out to again (we don't use the data today so why bring it into ORC). Archiving data for legal or general reference and then only converting the data we need to feels like a much better approach to me.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!