I would say yes, given my experience with ZFS of a number of years in production.
But even after a port, the underlying FS will have many more years of production use than brtfs. You might find bugs in the interface between the kernel and ZFS, but hopefully they wouldn't mess with any of the core fs code.
For instance, creating raid sets - by default it works with whole disks, which is exactly what you want 99% of the time (but you can specify a partition if you really want to).
Want to check whether there is a data corruption error?
"zpool scrub poolname" and it will go through all the disks on that pool, using the built-in ECC to verify that the data on the disks is OK. If not, it will try to fix it.
"zpool status -v" lists all the disks, which mirrors or RAID sets each is part of, and when the last scrub was performed, along with errors or ECC problems.
The one suggestion I would make for the btrfs guys is to really work on making the CLI commands simple and intuitive.
Also, since ZFS doesn't dedupe (just don't use it) or compress at rest, a scrub is the practical way to apply changes to those settings to the existing blocks already on disk.