What data comes across in a migration

What Kula can bring across depends on the system you are leaving. This article lists it record type by record type, so you can see before the migration starts what will arrive and what your team will need to rebuild.

Which systems Kula migrates from

Greenhouse and Ashby have the widest coverage, followed by Lever and Workable. If you are on one of those, expect most of the table below to apply.

Two entries are much narrower than their names suggest. UKG Pro brings across users and nothing else — if you are on UKG Pro, check whether you are actually on UKG Pro (HCM), which is a different connector with far broader coverage. Personio brings across candidates only.

What comes across, by record type

What never comes across

• Assessments. No source brings assessment records or results into Kula. If you need that history, export it from your current system before your contract ends.

• Your settings. Roles, permissions, interview plans, scorecard templates, application forms, career page and integrations are all set up fresh in Kula. A migration moves records, not configuration.

• Anything your current system will not release. If a record type is missing from your source's row above, it is because the data is not available to us, not because we chose to skip it.

Resumes and attachments on a file migration

For connected migrations this is simple: attachments come across.

For file migrations it depends entirely on what your export contains, and exports vary a great deal between providers. Ask your implementation contact to confirm against your actual export files rather than assuming either way — this is the single most common thing teams are surprised by after a file migration.

If resumes matter to you, raise them at the start. It is much easier to request a fuller export while your old contract is live. For more, see Prepare a file migration.

Good to know

• Coverage is per record type, not all-or-nothing. A source that does not bring interviews across still brings candidates and jobs.

• A missing record type is not a bug to report. If interviews are not in your source's list, they will not appear after the migration, and re-running will not change that.

• Custom fields come across as job post fields, from the eleven sources listed. Custom fields on candidates are not in scope.

• Your stage names come with your jobs where job stages are supported, so your pipeline structure carries over rather than being flattened into Kula's defaults.

• You do not have to take everything on offer. Many teams deliberately leave archived candidates behind. Tell your implementation contact what you want scoped out.

FAQ

Will our scorecards and interview feedback come across? From Ashby, Freshteam, Greenhouse, Lever and Trakstar, yes. From every other source, no — export what you need to keep before your old contract ends.

We're on Greenhouse. What won't we get? Candidate messages and communication templates. Everything else in the table above is supported, which makes Greenhouse the most complete migration Kula does.

Do our interview stages come across, or does everything land in one stage? Where job stages are supported for your source, your stage structure comes with your jobs. Check the job stages row above for your system.

We're migrating from UKG Pro and almost nothing is listed. Is that right? Check which UKG product you are on. UKG Pro brings across users only. UKG Pro (HCM) is a separate connector with much broader coverage, including candidates, applications, offers and notes. Your implementation contact can tell you which one applies.

Our assessment results are important to us. What are our options? They cannot be migrated from any source. Export them from your current system while your contract is live and keep them outside Kula, or attach the key documents to the candidate records after the migration.

Need help? If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.