Transfer Animals

required setup to use this feature, both the sender and receiver dairies must have pulse enabled contact us docid 4ghs 95g97ps fckkm8su if you are using dairycomp, but are not yet connected to pulse dairycomp unlimited dairies must enable a disposal code for record transfers go to dairycomp/mydc docid\ ezfejzdkbcfov b69aupr > settings docid\ vqytzmifem617 7ci4i9i > disposal codes docid\ crszzkmxa8wijdv 163rc and click the code to use be sure to use the enabled disposal code when entering a sold event for animals that are being transferred mydc dairies are configured to use disposal code 2 for record transfers by default when entering the sold event, be sure to select this code to transfer the animal records required permissions only users who are assigned to a role with herd write permissions can use this feature owners receive notifications regarding transfers via email see edit dairy user permissions docid\ gw6zx7tfc4ihsbrtozc v and manage dairy roles docid 9yjukdzfab0kko1hw0mxj for more information you can transfer animals and their associated records between two pulse enabled dairies or source farms this feature streamlines selling animals or merging herds by keeping data consistent across locations you can find this feature under the dairycomp/mydc docid\ ezfejzdkbcfov b69aupr > animals docid\ ezfejzdkbcfov b69aupr menu 🗒️ note use this feature for permanent relocations for recurring data sync with heifer growers, continue using itrans (iloop and dnt files) for animals with previous lactations, pulse sends data for all lactations automatically expand the topics below to learn more send animals to another dairy from the animal's list docid 4p0kb8foksptkzznqvho , a worklist docid\ vnfy2clldojhgpfvncgfl , or an open tasks docid co7 8k f9dieo 4fnodq list, select one or more animals to transfer you can also transfer individual animals from their cowcards docid\ fmnhz9tdqxw00vobpfalr add a sold event to the animal(s) and select the disposal code enabled for record transfer see disposal codes docid\ crszzkmxa8wijdv 163rc to learn more about this setting choose the destination dairy 🗒️ note if the destination dairy is set as discoverable in pulse, you can search for it by name or herdcode if it is not discoverable, you must enter the 8 digit herdcode manually contact the destination dairy if you do not have their herdcode see dairy info docid\ um11ovtjce3ar8qn7o4p2 to learn more about the discoverable setting select save the animals move to the sent animals tab if you made a mistake and need to cancel the transfer, see restore a transferred animal docid\ zlroglv75q9d41quuxfmt receive animals & map data the process for receiving animals is slightly different depending on whether your dairy is set to discoverable in pulse discoverable dairies automatically connect to receive transfers non discoverable dairies manually enter the 8 digit herdcode when initiating a transfer (if you do not have the herdcocde, contact the dairy ) the dairy owner then receives a connection request from the source farm via email (or in pulse notifications at the top of the page and in your message center docid\ tvk2rx3gfnaarni3sbolq ) after the dairy accepts the request, you can review animals pending transfer 🗒️ note see dairy info docid\ um11ovtjce3ar8qn7o4p2 to learn more about the discoverable option after the connection to the sender dairy is made, go to dairycomp/mydc docid\ ezfejzdkbcfov b69aupr > animals docid\ ezfejzdkbcfov b69aupr > transferred animals > pending receipt tab click the sender herdcode to view pending animals to review all animals together, check the box in the top row in the table map animal ids, events, sync date, and animal assignments as follows id click the toggle for all animals and then the edit icon to adjust an animal's id in your herd events dairycomp unlimited dairies can map events if the incoming animals have events that are named differently or do not exist in your dairy events for mydc dairies are automatically mapped if they are standard events any events left unmapped are not saved to the animal's cowcard see check connected farms & mapped events docid 906pnlwf0oydd3zkh4kqw to learn more about this process sync date choose whether or not to clear the animal's ovsynch enrollment date if both dairies are on the same ovsynch schedule, you can keep the same date to continue on the current protocol animal assignment assign a pen, enrollment date (edat), and enter the source farm information or a note 🗒️ note vas recommends the keeping the default enrollment date, which is the date the animal was added to your herd the note field is limited to 9 characters accept or reject each animal accepted animals are added to your animals list in pulse and added to your herd in dairycomp (for dairycomp unlimited dairies) rejected animals are returned to their original farm and pulse sends a notification to both dairy owners regarding the rejection check for pending transfers if your dairy has pending transfers, pulse shows notifications at the top of the page and in your message center docid\ tvk2rx3gfnaarni3sbolq click the link to review the pending or sent animals pulse also sends the dairy owner an email when animals are sent or received if transfers are not accepted or rejected within 10 days, pulse sends the dairy owner a reminder important distinctions event mapping dairycomp unlimited dairies have the option to map events if the sender dairy has different event names for instance, the sender dairy may have different vaccination event names, breeding event names, or custom health events event mapping allows you to match those unfamiliar events to ones your dairy does use, which preserves key animal data pulse saves your event mapping settings, so the next time you buy or receive animals from the same dairy, the transfers can be completed quickly mydc dairies have standard events, so transfers between mydc dairies will not require event mapping for transfers received by a mydc dairy from a dairycomp unlimited dairy, only standard items are automatically mapped if you choose not to map an incoming event, that event is not saved to the animal's record you can map multiple events from the sender dairy to the same event in the receiver dairy for instance, the sender dairy may have multiple vaccination events, and the receiver dairy has only one event, vacc see check connected farms & mapped events docid 906pnlwf0oydd3zkh4kqw to learn more discoverable dairies discoverable dairies automatically connect to receive transfers non discoverable dairies manually enter the 8 digit herdcode when initiating a transfer (if you do not have the herdcode, contact the dairy )the dairy owner then recives a connection request from the source farm via email (or in pulse notifications at the at the top of the page and in the message center docid\ tvk2rx3gfnaarni3sbolq ) after the dairy accepts the request, you can review animals pending transfer 🗒️ note see dairy info docid\ um11ovtjce3ar8qn7o4p2 to learn more about the discoverable option transferring animals in dairycomp dairycomp unlimited dairies can also manually move animals in dairycomp using the putcow and getcow commands, but vas recommends using pulse for standard animal movements between dairies to benefit from the following a guided workflow automated data mapping safety checks to prevent duplicate records reserve the getcow/putcow commands in dairycomp for technical file operations, such as manually recovering a specific animal record from a backup or archive file see transfer animals from one dairy to another docid\ a6gvpgg7c yuihp0iqhcx to learn more about moving animals in dairycomp