Short answer: packs aren’t auto-applied to the world

If your Java world uses data packs (datapacks) or resource packs, let’s be clear up front: they will not be automatically moved into the Bedrock world during conversion. The reason is that the mechanics differ — a Java data pack changes game logic (functions, loot tables, custom crafting, advancements, etc.), while a Java resource pack changes appearance (textures, sounds, models). Bedrock’s equivalents are behavior packs and resource packs, but the format, directory structure, and loading method are all different, with no one-to-one automatic conversion.

The TopoBlocks Java → Bedrock conversion migrates the world file itself: terrain, the vast majority of blocks, container contents, and structure layouts can usually come across. Changes brought by data packs/resource packs, meanwhile, are written into an item-by-item change report that tells you exactly which mechanics can’t be migrated automatically and need to be handled separately on Bedrock — we never promise ‘100% lossless,’ nor do we pretend we can convert packs over with one click.

Data packs and resource packs: what happens to each after conversion

  • Data packs (logic). Blocks and structures already generated by a data pack in the world will migrate along with the world; but ‘logic that keeps running via a data pack’ (such as custom crafting, functions, looping commands) is a Java-only mechanic and must be rebuilt differently with a behavior pack on Bedrock. The report flags this part, so it won’t quietly disappear in the background.
  • Resource packs (appearance). Java resource packs can’t be read directly by Bedrock. To keep the same textures/sounds, you’ll need to find or create a corresponding Bedrock resource pack. The conversion won’t package textures for you, but the report will note which assets the original world referenced so you can match them up.

If you want to first understand what behavior packs and resource packs each handle, see what behavior packs and resource packs are and how they differ.

How to add these packs back on Bedrock

After the conversion finishes and you have the item-by-item report, handle things separately on Bedrock following the report:

  1. Appearance: import or create the corresponding resource pack on Bedrock. Bedrock packs are usually distributed as .mcpack / .mcaddon; see what .mcpack and .mcaddon are.
  2. Logic: rebuild the gameplay implemented by a data pack in an equivalent way using a Bedrock behavior pack — this step requires you to rewrite it for Bedrock’s mechanics, and no automatic tool can skip it.

A few baselines are worth repeating throughout this process: conversion is pay-per-use with automatic refunds on failure, and pricing is as shown in the app; and your source files are never overwritten — the original Java world, hash included, is preserved and traceable, so even if you’re unhappy with the conversion result, your original save is always safe. To understand exactly what of the world’s core can and can’t migrate, it’s reassuring to read what transfers and what doesn’t when converting Java to Bedrock again.