<?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: Integration: Issue importing mobile numbers from Apollo in Third-Party Apps</title>
    <link>https://community.hubspot.com/t5/Third-Party-Apps/Integration-Issue-importing-mobile-numbers-from-Apollo/m-p/1184371#M913</link>
    <description>&lt;P&gt;I’ve run into this exact headache before. Even if you set the mapping correctly in Apollo, sometimes the way Apollo pushes updates via their API still ends up overwriting the main Phone Number field in HubSpot when you update Mobile. It’s like Apollo treats both as the primary by default.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What helped us was double-checking if Apollo’s integration is actually using a full update instead of just updating the specific field. If you’re on the standard mapping, Apollo often does a blanket overwrite for contact info. Try reaching out to Apollo support and specifically ask if they can set up field-level updates on your account, so only Mobile touches Mobile, and nothing else.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One other trick: if you do batch updates in Apollo, sometimes the field mapping sticks properly, but single contact pushes (like manual enrichment) are more prone to overwriting. So, test a small batch.&lt;/P&gt;</description>
    <pubDate>Sat, 02 Aug 2025 16:58:20 GMT</pubDate>
    <dc:creator>ASam26</dc:creator>
    <dc:date>2025-08-02T16:58:20Z</dc:date>
    <item>
      <title>Integration: Issue importing mobile numbers from Apollo</title>
      <link>https://community.hubspot.com/t5/Third-Party-Apps/Integration-Issue-importing-mobile-numbers-from-Apollo/m-p/1031205#M103</link>
      <description>&lt;P&gt;We've been using Apollo for our contact information enrichment and have run into an issue with importing mobile or direct numbers. When we request the direct dial and push the number into HubSpot, it also overwrites the Phone Number that is listed in HubSpot.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I confirmed that our field mapping is correct within Apollo - each phone number option (Phone, HQ, Mobile) is mapped correctly to different fields within HubSpot. However, every time I push the mobile number from Apollo into HubSpot, the number writes into the Mobile Number field AND overwrites any existing Phone Numbers the other field.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone encountered this before, or have a solution?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 22 Aug 2024 23:41:57 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Third-Party-Apps/Integration-Issue-importing-mobile-numbers-from-Apollo/m-p/1031205#M103</guid>
      <dc:creator>amangels</dc:creator>
      <dc:date>2024-08-22T23:41:57Z</dc:date>
    </item>
    <item>
      <title>Re: Integration: Issue importing mobile numbers from Apollo</title>
      <link>https://community.hubspot.com/t5/Third-Party-Apps/Integration-Issue-importing-mobile-numbers-from-Apollo/m-p/1184371#M913</link>
      <description>&lt;P&gt;I’ve run into this exact headache before. Even if you set the mapping correctly in Apollo, sometimes the way Apollo pushes updates via their API still ends up overwriting the main Phone Number field in HubSpot when you update Mobile. It’s like Apollo treats both as the primary by default.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What helped us was double-checking if Apollo’s integration is actually using a full update instead of just updating the specific field. If you’re on the standard mapping, Apollo often does a blanket overwrite for contact info. Try reaching out to Apollo support and specifically ask if they can set up field-level updates on your account, so only Mobile touches Mobile, and nothing else.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;One other trick: if you do batch updates in Apollo, sometimes the field mapping sticks properly, but single contact pushes (like manual enrichment) are more prone to overwriting. So, test a small batch.&lt;/P&gt;</description>
      <pubDate>Sat, 02 Aug 2025 16:58:20 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/Third-Party-Apps/Integration-Issue-importing-mobile-numbers-from-Apollo/m-p/1184371#M913</guid>
      <dc:creator>ASam26</dc:creator>
      <dc:date>2025-08-02T16:58:20Z</dc:date>
    </item>
  </channel>
</rss>

