Having a nightmare dealing with getting Documents from Hubspot to Nutshell or just Export. I’m told it’s possible, just not able to get there thus far. Looking for a one-time export/transfer help and get bids.
4 Likes
Hello @RayRoberts , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications
Hey @RayRoberts , I can handle this as a one-time export/transfer job. The first step is confirming where the HubSpot documents actually live and how they need to land in Nutshell, since the method changes depending on whether they’re attachments, files, notes, or documents tied to records. I’d use the fastest reliable path available, either through HubSpot and Nutshell APIs directly or via Make for a controlled export and transfer. If Nutshell import limits get in the way, I can also deliver a clean structured export with the files and record mapping preserved. This is the kind of issue that’s usually solved quickly once I can inspect the object type and sample records. Send me the document source details, the target in Nutshell, and whether you want transfer or export only, and I can scope it immediately. Feel free to book a meeting with me here to discuss this further.
Ray,
CRM document transfers are one of those jobs where “it should export” and “it exported in a usable way” are two very different things. I can help you get this untangled cleanly, either by pulling the documents out of HubSpot into a structured export or by mapping them into Nutshell without losing the record relationships that make the files useful.
I would approach it like this:
-
I would first identify exactly where the documents live in HubSpot, because files attached to notes, deals, companies, contacts, emails, and HubSpot Sales Documents are not always accessed the same way.
-
I would confirm whether your real need is a full migration into Nutshell, a clean standalone export, or both. That affects the level of mapping, testing, and cleanup required.
-
I would review a sample set of records before doing the full export so we can see whether HubSpot is returning direct files, private file links, attachment metadata, or incomplete associations.
-
I would build a document inventory before moving anything. That would include file name, source record, associated company or contact, HubSpot object type, upload date where available, and source URL.
-
I would check Nutshell’s import limitations early so we do not waste time preparing a format that Nutshell cannot accept.
-
I would create a small test transfer with a few records first. If the documents land correctly and stay tied to the right records, then I would scale the process.
-
I would watch closely for duplicate files, because CRM exports often show the same document through multiple associations. Blindly moving everything can create a bigger mess.
-
I would preserve the original folder or relationship logic as much as possible. If Nutshell cannot accept the files directly, I would still deliver a clean folder structure with an index file so the export is usable.
-
I would separate failed or restricted files into an exception report instead of burying them. You need to know what moved, what did not, and why.
-
I would keep this as a controlled one-time job, not an open-ended integration project, unless you decide later that you want ongoing sync or automation.
Relevant experience:
DocuMind.ai
I built a document intelligence workflow for ingesting PDFs and Word files, converting unstructured documents into searchable, organized data. That is directly relevant here because the real work is not just grabbing files from HubSpot. It is making sure the documents remain traceable, organized, and useful after export.
FraudShield Document Analysis Platform (efraudservices.com)
I worked on a platform for uploading, processing, and organizing financial PDFs through OCR and structured review workflows. My role involved handling document ingestion, file processing, structured data extraction, and human review paths. That experience ties closely to your issue because CRM document exports usually need validation, cleanup, and exception handling before the output can be trusted.
I built a SaaS platform that pulled and normalized data from multiple third-party APIs, including property data sources with inconsistent fields and record structures. That matters here because HubSpot to Nutshell is not just a file task. It is an API and mapping task where record relationships, IDs, associations, and destination limitations have to be handled correctly.
Background Screening SaaS Platform (https://stage.drugscreening-fe.testyourapp.online/)
I helped modernize a legacy workflow by connecting a new web platform to an older operational system through structured API handling and fallback processes. That is relevant because if Nutshell cannot accept every document cleanly, the job still needs a practical fallback that gives you a reliable export instead of leaving you stuck halfway through the transfer.
I can help you get this done in a clean, controlled way. I would be happy to take a quick look at the current HubSpot setup, confirm the document source, and then give you a fixed bid for the export or transfer.
A few questions I would want to confirm:
-
Are the documents attached to contacts, companies, deals, notes, emails, or HubSpot Sales Documents?
-
Do you need the files imported into Nutshell, or is a clean export acceptable?
-
Roughly how many records and documents are involved?
-
Do the documents need to stay tied to specific companies, contacts, or deals?
-
Do you already have admin or API access to both HubSpot and Nutshell?
Brandon
brandon@bluegrass-media.com
501-733-1465
Hi @RayRoberts! I would love to help you with this automation.
We are a small team of make.com experts and have developed plenty of complex integrations. This project should not be a challenge to us.
If you are interested we would love to help you, you can schedule a call in here: https://cal.com/aspirity/discovery?utm_source=make discovery or check our website www.aspirity.com
Hi Ray, welcome to the Make community.
This is usually a mapping/file access issue between HubSpot and Nutshell…I’ve handled similar exports and transfers before.
This can be done as a clean one-time export or a direct transfer using Make.
Quick one:
are you moving actual document files or just the records/links?
Happy to help get this sorted.
Email: folafoluwaolaneye@gmail.com
Book a call: https://cal.com/folafoluwa-olaneye-osrofp/30min
I can help you get this done cleanly.
I’ve handled exports and migrations between HubSpot and Nutshell, including pulling documents/attachments that aren’t straightforward via native export.
I’ll:
Extract all required documents (API or workaround if needed)
Map and prepare them for Nutshell
Complete the transfer or deliver a structured export
One-time job is fine.
Is this job still available?
If so, send me what you’ve tried so far + access details, and I’ll take it from there.
Email: fopefoluwaakinola@gmail.com
Hi!
I can help you end that “nightmare.” Migrating documents between CRMs like HubSpot and Nutshell is tricky because you aren’t just moving text—you’re dealing with file attachments, public vs. private URLs, and mapping them to the right contact or deal.
How I’ll solve this for you:
-
The Export: I’ll use the HubSpot API to pull not just the metadata, but the actual file binary or hosted URLs.
-
The Transfer: I’ll build a script (likely in n8n or Python) to map those files directly into the corresponding records in Nutshell.
-
Validation: I’ll run a check to ensure every document is attached to the correct person so nothing gets lost in the “void.”
The Deal:
-
Estimated Bid: For a one-time migration, I’d bid $300 – $500, depending on the volume of documents and how “clean” the mapping needs to be.
-
Timeline: I can get this finished in 24–48 hours once I have access.
-
Availability: I have 25–35 hours a week free and can start right now.
Why me?
I’m Mikhail, a developer and automation specialist. I deal with “messy” data migrations all the time—specifically using SQL, APIs, and n8n to move information between platforms that don’t want to talk to each other.
Portfolio: https://mikedevai.netlify.app/
Contacts:
-
Telegram: @hely_chatbots
-
WhatsApp: +375293761570
Let’s get those files moved so you can stop worrying about it!
Best,
Mikhail (Mike) Rogal
Hi Ray,
HubSpot doesn’t make document exports obvious, and Nutshell’s import options are limited, so most people end up with either broken links, orphaned files, or records that don’t map correctly.
HubSpot handles attachments on deals/contacts differently from files in the Documents library or notes with embedded files, and the extraction method changes depending on that.
Once I know that, I can handle the transfer cleanly and delicately via the API’s or via Make.com if you prefer a visual and repeatable flow.
I can scope this in one short call or async over a few messages if you share the document source and volume.
One-time job is completely fine.
Victoria | Book a call
Hey @RayRoberts,
Have sent you a DM as well. Would love to help you migrate from Hubspot to Netsuite. I run an automation studio called Automation Jinn where we help companies automate their processes and increase efficiency. I am Make advanced certified, and Hubspot Sales/Marketing Hub certified with a background in computer science so quite comfortable in integrating API and custom code. I have experience working with both SMB’s and large enterprises.
Some of my relevant work-
• For a fintech startup in Amsterdam (raised €8.1M), automated there lead flows in the CRM and built a custom Slack bot to flag churn risks.
• Built a workflow that enriches and qualifies inbound leads using Bright Data MCP while updating the CRM in Hubspot for both qualified and unqualified.
• For an education company, I integrated LMS with Airtable, Make, and their CRM via API handling complex pagination and syncing data in real time.
I work more as an AI transformation partner for my clients rather than just a builder. Would love to learn about your day to day operations 
Happy to also jump on a call if it’s easier- https://cal.com/sparsh-gupta-pnrp6p/30min
Cheers,
Sparsh
Founder
Automation Jinn
Hi Ray — happy to help. Two-part shape for one-time HubSpot → Nutshell document migrations:
-
HubSpot extraction. Files API gets the file binaries. Documents (Sales Hub Documents specifically) is a separate object — confirming which one you mean is part of scoping, since the export path differs. Heads-up: the HubSpot v3 Files API rate-limits on download URLs more aggressively than on metadata fetches, so the migration script needs back-off.
-
Nutshell ingestion. Nutshell’s REST API covers contacts / leads / companies / notes well. Direct file-attachment via API is the part I would verify against your account before quoting (their docs are thinner there than HubSpot’s). If the API path does not cover it, fallback is bulk file export from HubSpot + import via Nutshell’s bulk-import flow with file references.
-
CSV manifest of every file moved + status (success / skipped / failed) — re-runnable so you can retry only the failures.
A few things that determine the price:
- Roughly how many documents — 100? 1,000? 10,000+? (changes API back-off + total run time)
- What “documents” specifically — uploaded files, signed Sales Hub Documents, generated PDFs from templates, or attached notes?
- HubSpot custom properties on documents — preserve on the Nutshell side?
- One-shot run, or fully re-runnable script?
Email priyanshukumarmaurya2224@gmail.com with answers. I will verify Nutshell’s exact file-attachment capability against your account, then send a fixed quote + 2-3 day timeline.
Background: shipped a similar Clio Manage API import (police-report PDFs → law-firm CRM with full metadata preservation) plus a multi-system data sync engine on Make.com. PDF + CRM API work is daily.
— Priyanshu Kumar
linkedin.com/in/priyanshu-axiom · https://priyanshukumar.co/