How to Map Company and Contact Fields in Sage Intacct
Learn how company and contact field mappings affect your Sage Intacct integration workflow.
⚙️ Step 1: Open the Customer Module
-
Go to the Customer module.
-
Click View Mapped Fields.
-
At the bottom, you’ll see the required fields by Sage Intacct — these must be mapped for the integration to function correctly.
⚠️ These required fields must be completed on the Intacct side for data to push or pull successfully between FollowUp and Sage Intacct.
🔗 Step 2: Understand Company and Contact Field Mapping
At the top of your mapped fields window, you’ll see Company Fields, and below that, Contact Fields.
This represents the crossover between FollowUp Companies and FollowUp Contacts.
You can map fields to:
-
🏢 Company fields — related to the organization.
-
👤 Contact fields — related to the individual contacts under that company.
🧭 Step 3: Workflow Option 1 — Company Fields Only
If you only map company fields (and no contact fields):
-
You do not need to select a contact when pushing a record to Sage Intacct.
-
The integration pushes data from the company record alone.
🧠 Example:
You push a FollowUp company called Silver Peak Development to Sage Intacct.
Even if multiple contacts exist under that company, the integration will work the same way regardless of which contact is selected — because contact fields are not mapped.
✅ Whether you select Drew or Harper as a contact, both will sync successfully since only company fields are mapped.
🔁 Step 4: Workflow Option 2 — Company and Contact Fields
If you map any contact fields, such as Contact Name:
-
The system will require you to choose a specific contact during the push.
-
This ensures the mapped contact data (like name, email, or phone) syncs accurately to Sage Intacct.
🧩 Example:
-
Map the Contact Name field.
-
When pushing the company, you’ll be prompted to choose which contact to sync.
-
Select a contact (e.g., Sam) and push.
-
The system records that this company was synced with Sam specifically.
If you later check the company record, you’ll see that it displays Sam as the connected contact.
🧱 Step 5: How Contact Mapping Affects Projects
When working within the Projects module:
-
If a contact is mapped, you’ll be required to select that same contact for project syncing.
-
If you choose a different contact that’s not connected, you’ll receive a message stating:
“The selected contact is not connected.”
🧠 Example:
-
If Sam is the contact that was synced with the company, and you choose Reese when pushing a project, the system will notify you that Reese isn’t connected.
-
However, if you proceed, the integration will still push and automatically update the contact in Sage Intacct to Reese.
⚙️ Step 6: Adjust According to Your Team Workflow
This behavior depends entirely on your field mapping setup between companies and contacts.
👉 If your team relies heavily on contact-specific data (e.g., individual client relationships), you should map contact fields.
👉 If your workflow is focused on company-level data, you can map only company fields to simplify the process.