Outline

This explains the data migration process for clients who wish to transfer data from their existing job platform to a new Madgex job board. The process follows a number of steps, detailed below.

It will require a minimum of two data backups being supplied by the client: at the start of the project (for data analysis) and just before launch (for the live data migration). This data can be supplied via a secure FTP space, or possibly by other means if appropriate for the amount of data being sent. Please discuss this with your Project Manager.

One of the most important points of the entire project is that the data supplied on these two occasions is supplied to Madgex in exactly the same format. Any deviation from this can result in delays, or multiple data errors, at the time of launch.

Analysis

For analysis, Madgex requires, as soon as possible at the start of the project, a sample of your dataset. This can be either a sample or a full data backup.

If your data is held and managed by a third party, it is crucial that you contact that third party as soon as possible, informing them of the migration to another platform, and of the two data deliveries that you will require.

It's important that all data types are included in the sample or full backup. This means that it should include every element that you are expecting to be migrated to the new job board, and is likely to include most or all of the following:

• Users (Jobseekers, Recruiters / Employers, and Administrators)
• Jobseeker profile details
• Jobseeker CVs / Resume Documents
• Job alerts
• Recruiter company details
• Logos (preferably 360 pixels x 180 pixels, but other sizes can be asjusted for)
• Creditsets (if these are currently assigned to recruiter / employer accounts
• Job details (individual job descriptions)
• Job taxonomy (categorisations)
• Job applications
• Any documents attached to applications

On receipt of this data, Madgex will complete a high-level sanity check to ensure the data can be successfully migrated.

Note that the following data cannot be migrated:

• Statistics from your current site
• Financial Information such as Basket details or Transactions
• Any product promotions
• Any existing mini-sites that your job board may include
• Static page content, or other content such as articles
• External ads from third party suppliers, such as Goole Ads

Specification

Madgex will then produce and return a Data Migration Specification which will identify: 

• Every field that can be migrated
• Any data mappings required
• Any concerns, comments or questions from Madgex about the data

Note that any data not referenced in the document will not be migrated.

Mappings

Madgex will also produce a Mappings Document which will identify:

• Job classifications (how existing job categories will be mapped to new job categories)
• Job alert classifications (similar to above, but for job alerts)
• Jobseeker question responses (if relevant, and if new responses differ from the current ones)

Madgex will probably need your input to complete these mappings as not all values are likely to be obvious.

If you also require any existing recruiter products (i.e. job ad packages that you are currently offering to recruiters online) then please request a Recruiter Product Migration document from your Project Manager.

Scripting

Once the above Specification and Mappings are agreed on, Madgex will prepare the import and migration scripts for the full data migration process.

Testing

At an agreed point during the User Acceptance Testing of the new job board, Madgex will initiate a test migration into the new test sites, running all processes at they would be for launch.

The migration of the original data supplied can then be tested within the new, test sites, issues identified and adjustments made to the scripting.

Once all adjustments are complete, and the test migration re-run if necessary, you will be asked to signoff on the data migration, ready for the live process to be carried out prior to launch.

Launch

A Launch Plan will be agreed with you, outlining dates and estimated times for the data migration and launch tasks.

Prior to launch you will be asked for a final, full data cut, for migration into the pre-live sites. It is essential that this data is supplied to Madgex in exactly the same format, and by the same process, as that agreed on during the migration test period. If the format of the data deviates in any way from the format during testing, the migration scripts will break resulting in live migration errors, or even complete failure of the migration.