If your migration is paused and you see a message on the wizard page, it likely means your source or target CRM has API call restrictions. You can check the details below the error to determine what CRM has hit the limit.
What Are API Call Limits?
API call limits define how many times an application (like the migration tool) can connect to a CRM in a certain time frame—usually per hour or per day. Since the migration tool transfers data by sending API requests, it's subject to these limits.
Some CRMs, especially those with basic or free plans, have low API call limits. To find out your specific limits, check your CRM's knowledge base or contact their support team.
Why This Affects Your Migration
While the migration tool is optimized to send data in bulk to minimize API usage, some objects—like chatter posts or files—still require separate API calls per record due to CRM limitations. So, even if your daily limit seems high, it can be quickly reached when migrating large datasets or if other apps are also using your CRM's API at the same time.
How the Migration Tool Handles This
The tool monitors API usage and automatically pauses when the limit is hit. However, API limits usually reset gradually based on how they were used. For example, if the tool used 100,000 calls over 24 hours (about 4,200 per hour), the limit will refresh at roughly the same rate—giving you back some calls every hour.
The migration tool checks for available API calls every hour and will resume automatically from where it left off once limits are renewed.
What You Can Do
-
If you know that no other applications are using the API calls and you are not in a rush: Simply wait. The migration will continue on its own once calls become available again.
-
If this affected the other applications that are using API calls and you need it to finish sooner: Contact your CRM support team and ask if they can temporarily increase your API call limits. The migration will resume automatically within an hour of the limit being lifted.