When your job board moves to Jobiqo, all or some of your data (recruiters, jobs, applications, and more) is transferred to your new system. Before you go live, check that everything came across correctly and works the way your team and users expect. Also check that no data was migrated that should not have been, for example data outside the agreed cutoff, such as anything older than two years.
This guide takes you through the testing step by step, from understanding what was migrated to signing off on the results.
We recommend testing in two ways:
- Does the data match? Compare your new system with your old one, field by field.
- Does everything still work? Try the everyday actions of recruiters, applicants, and site admins.
Step 1: Confirm your migration scope
Before you start, check which data objects are part of your migration. You can find this in your contract with Jobiqo. Not every client migrates every object. Your scope can include:
- Users (recruiters, applicants)
- Organizations (profiles, locations, contact persons, relations)
- Jobs (per template, per file, per link, plus upgrades)
- Applications
- Resumes (with work experience and education)
- Commercial data (subscriptions, credits)
- Content (blog, SEO search content)
- Job alerts
- Job performance data (analytics)
- SEO redirects
Step 2: Prepare your test
- Compare totals. Compare the number of recruiters, applicants, organizations, active jobs, and so on in the old and the new system.
- Choose your sample. You decide how many records to test. Include complex cases as well as simple ones. Examples: organizations with several locations, upgraded jobs, and recruiters who belong to more than one organization.
- Share the work. If several people test, give each data object or workflow to one person.
- Keep a test log. For every issue, write down the account you used, the exact record, and what did not match.
Note: Matching totals are only the first check. Numbers can match even when values or links are wrong, so continue with the detailed checks in Step 3.
Step 3: Test the data
Check each record in your sample against the list below.
| What to check | What to look for |
|---|---|
| Required fields | Every recruiter and applicant has a unique email. Every organization has an owner. Every job has a title. |
| Dates | Dates show the original creation and update times, not the migration date. The exception is when the old system had no value. |
| Single-option fields | Fields such as salutation or workflow state have a value. They are not blank or set to a default. |
| Content and media | Open a sample of organization profiles, blog posts, and job descriptions. Check that they display correctly. Files such as logos, images or CV documents are available, if they were part of your migration. |
| Data that should not be there | No data outside your agreed cutoff (for example, older than two years), no test accounts, and no duplicates. |
Check relationships
Relationships are easy to overlook. Confirm that:
- Organizations have the correct owner.
- Recruiters belong to the correct organization.
- Parent-child and agency relationships between organizations are intact.
- Jobs link to the correct organization and author.
- Applications link the correct applicant to the correct job.
- Resumes, work experience, and education belong to the correct applicant.
Check special cases
| Case | What to check | Example |
|---|---|---|
| Special characters | Accented letters, special characters and non-Latin scripts display correctly on the whole site, not only in the admin area. | e.g. ü, é, ñ, €, ™, ©, ц, λ, η, ά, — |
| Rich text formatting | Allowed formatting displays correctly in job descriptions, company profiles, applications, and emails. HTML tags are rendered, not shown as code. |
<strong>Senior Developer</strong> appears as Senior Developer
|
| Empty and very long values | Empty optional fields do not cause errors. Very long titles and descriptions are not cut off. | A job with no salary. A job title with 150 characters. |
Step 4: Test the taxonomy mapping
Do this step if your taxonomy changed during migration. Test it separately, because taxonomy problems can be hard to spot in job and CV records.
What is taxonomy mapping?
Jobiqo uses taxonomies (controlled lists) for fields such as occupation, industry, employment type, experience, skills, and languages. During migration, each term from your old job board is mapped to a term in the new system.
A mapping can do the following:
| Mapping type | Example |
|---|---|
| Rename a term | "Human Resources" → "Human Resources Management" |
| Merge terms | "Head of HR" and "HR Generalist" → "Human Resources Management" |
| Remove a term | The term is deleted. Its data is reassigned or deleted. |
| Add a term | A new term is created. |
| Create a parent-child structure | "Head of HR" becomes a child of "Human Resources Management" |
What to test
- Renamed and merged terms: Records that used the old terms now show the correct new term.
- Removed terms: They no longer appear in filters, dropdowns, or tag lists. Their data was reassigned or removed as planned.
- Parent-child structure: Child terms appear under the correct parent.
- New terms: They can be selected. If they already have data, check that it is tagged correctly.
- All taxonomy fields: Test every field that had to be mapped, not only occupation.
- Display across the site: Each taxonomy term displays and filters correctly on job details, search, CVs, and company profiles.
- Free-text fields: For fields like skills or languages that allow custom values, confirm that existing entries were correctly migrated.
Step 5: Test the workflows
Use the Checklist for Standard Workflows to test all three user types
| User type | What to test |
|---|---|
| Applicants | Register or log in, complete a CV, search for jobs (including taxonomy filters), create a job alert, bookmark a job, reset the password. |
| Recruiters | Register or log in, complete the organization profile, post a job, tag it with the new taxonomy, buy an upgrade, view posted jobs, request applicant contact details, check the dashboard. |
| Site admins | Add credits and post jobs on behalf of a client, view and export orders, export users, add taxonomy synonyms, manage landing pages, create and redeem discount codes. |
Step 6: Report issues and sign off
Report an issue
Collect your issues in your test log first, then send them to your Jobiqo Project Manager. A single list helps Jobiqo find patterns and fix related issues in one go. If something blocks your testing, tell your project contact right away. Include the following:
- The account you used
- The page URL
- What happened
- What you expect to happen
- Whether you consider it a data or a workflow issue
Please do not include personal applicant data in your report. A record ID or a screenshot is enough.
Check the fixes
When Jobiqo has fixed an issue, check the same record again. Also check a few related records.
Sign off
When your sample checks and all three workflows are complete, confirm the sign-off to your project contact. Keep your test log for reference after go-live.
Questions? If you have a question about a specific field, data object, or taxonomy mapping, contact your Jobiqo Project Manager.