It is not currently possible to re-parent Chatter Feed records or move them from one record to another via an update operation. The FeedItem object's ParentId field, which stores the ID of the record to which a feed item is related, does not support update operations in Salesforce.
To work around this limitation, you can recreate the posts and associate them with the new parent record. The process requires you to export the Chatter posts and comments using Data Loader, update the CSV files to reference the new record ID, and then insert new Chatter Feed posts and comments on the destination record. Once the content has been recreated on the new record, delete the original feed items from the source record.
Perform two separate exports on the FeedItem and FeedComment objects.
You will have two CSV files containing the Chatter records associated with the source record. Review these files and remove any posts or comments you do not want to move.
Note: Save a copy of the original files to a safe location for backup purposes.
Use Data Loader to perform an Insert on the FeedItem object using the updated FeedItem CSV file.
The Data Loader success file from Step 3 contains the new FeedItem IDs alongside the original IDs. Use this file to map old FeedItem IDs to new ones.
In the FeedComment CSV file, create a new column called FeedItemID and insert the new FeedItem record IDs from Step 4, matching each comment to its corresponding new FeedItem.
Use Data Loader to perform an Insert on the FeedComment object using the updated FeedComment CSV file.
Use the Old FeedItem ID and Old FeedComment ID values to delete the original Chatter feed posts and comments from the source record using Data Loader's Delete operation.
If the logged-in user has the "Insert System Field Values for Chatter Feeds" user permission, the create field property is available on CreatedBy and CreatedDate system fields for the FeedItem object. This allows the logged-in user to set these fields to the original post author and creation date during migration, instead of defaulting to the logged-in user and the migration date. These fields cannot be updated after migration.
000387796

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.