<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Convert Custom ArcMap .tbx to Pro 3 .atbx in Geoprocessing Questions</title>
    <link>https://community.esri.com/t5/geoprocessing-questions/convert-custom-arcmap-tbx-to-pro-3-atbx/m-p/1360927#M27090</link>
    <description>&lt;P&gt;Dan,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yeah, that's what I kinda figured I was going to have to do, but was hoping that I could just write some quick code and, voila!, it's imported and I can go on to the other laundry list of things on this upgrade.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Appreciate it.&amp;nbsp; Thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 14 Dec 2023 15:53:16 GMT</pubDate>
    <dc:creator>BartPittari</dc:creator>
    <dc:date>2023-12-14T15:53:16Z</dc:date>
    <item>
      <title>Convert Custom ArcMap .tbx to Pro 3 .atbx</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/convert-custom-arcmap-tbx-to-pro-3-atbx/m-p/1360915#M27088</link>
      <description>&lt;P&gt;I'm in the early stages of a migration project from ArcMap 10.8 to ArcPro 3.x.&amp;nbsp; Moving the .mxds are not an issue, but we have a few .tbx files that were created for some customized projects (use/call Python 2.7 scripts with the toolbox taking in parameters).&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've used/am using the 2to3 conversion to migrate those scripts to Python 3.x, and was wondering if there was some way to programmatically convert the .tbx structure itself to an .atbx ... I thought ImportToolbox would be the way to go, but I may have been mistaken (got a 99998 error when I attempted).&amp;nbsp; If the Toolbox needs to be rebuilt, that's fine, but it looks like you can import from 2.x to 3.x so I figured there might be a way to migrate from 10.8 to 3?&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2023 15:37:24 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/convert-custom-arcmap-tbx-to-pro-3-atbx/m-p/1360915#M27088</guid>
      <dc:creator>BartPittari</dc:creator>
      <dc:date>2023-12-14T15:37:24Z</dc:date>
    </item>
    <item>
      <title>Re: Convert Custom ArcMap .tbx to Pro 3 .atbx</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/convert-custom-arcmap-tbx-to-pro-3-atbx/m-p/1360922#M27089</link>
      <description>&lt;P&gt;I copied the tools from the *.tbx into a new *.atbx in Catalog (right-click copy, then past&lt;/P&gt;&lt;P&gt;You have to redefine the toolset names.&lt;/P&gt;&lt;P&gt;The procedure wasn't without the odd glitch but was easier than respecifying tool parameters.&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2023 15:42:58 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/convert-custom-arcmap-tbx-to-pro-3-atbx/m-p/1360922#M27089</guid>
      <dc:creator>DanPatterson</dc:creator>
      <dc:date>2023-12-14T15:42:58Z</dc:date>
    </item>
    <item>
      <title>Re: Convert Custom ArcMap .tbx to Pro 3 .atbx</title>
      <link>https://community.esri.com/t5/geoprocessing-questions/convert-custom-arcmap-tbx-to-pro-3-atbx/m-p/1360927#M27090</link>
      <description>&lt;P&gt;Dan,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yeah, that's what I kinda figured I was going to have to do, but was hoping that I could just write some quick code and, voila!, it's imported and I can go on to the other laundry list of things on this upgrade.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Appreciate it.&amp;nbsp; Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 14 Dec 2023 15:53:16 GMT</pubDate>
      <guid>https://community.esri.com/t5/geoprocessing-questions/convert-custom-arcmap-tbx-to-pro-3-atbx/m-p/1360927#M27090</guid>
      <dc:creator>BartPittari</dc:creator>
      <dc:date>2023-12-14T15:53:16Z</dc:date>
    </item>
  </channel>
</rss>

