function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion

BUG: Migration Tool - "Cannot rename standard profile"

I'm trying to move a custom field from one sandbox into another using the Migration Tool, and getting a funky "Cannot rename standard profile" error.  


Here's my package file which goes in the "$PROJECT_ROOT/unpackaged" folder:



<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="">




Here's my ant build.xml file which sits in the $PROJECT_ROOT folder:



<project name="Sample usage of Salesforce Ant tasks" default="test" basedir="." xmlns:sf="antlib:com.salesforce">
    <property file=""/>
    <property environment="env"/>

    <target name="retrieveUnpackaged">
      <mkdir dir="retrieveUnpackaged"/>
      <sf:retrieve username="${sf.username}" password="${sf.password}" serverurl="${sf.serverurl}" retrieveTarget="retrieveUnpackaged" unpackaged="unpackaged/package.xml"/>

    <target name="deployUnpackaged">
      <sf:deploy username="${sf.deploy.username}" password="${sf.deploy.password}" serverurl="${sf.deploy.serverurl}" deployRoot="retrieveUnpackaged"/>



This properties file all goes in the $PROJECT_ROOT folder:




sf.username = <username>@<org>.sandbox1
sf.password = <password>
sf.serverurl =

sf.deploy.username = <username>@<org>.sandbox2
sf.deploy.password = <password>


To run, execute the following two commands:



ant retrieveUnpackaged
ant deployUnpackged



When I try to deploy to the second sandbox I am getting the following error:



Error: profiles/Guest License User.profile(Guest License User):Cannot rename standard profile



My package is pretty straightforward and I can't imagine what I might be doing to get this error.  Any thoughts?






I've confirmed with Salesforce support that this is indeed a bug with the Migration Tool and they've promised a fix sometime within the next two cycles of Halley's comet. 


Sooner would be better. It's biting me too :-(


Seems not to be fixed yet.


Resolution is to remove Chatter, Guest, and Portal user Profiles from deployment package.